Propose a patch

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -40,1 +40,0 @@
-To ensure Claude Code prioritizes Docy for documentation-related tasks, add the following guidelines to your project's `CLAUDE.md` file:
@@ -136,1 +135,0 @@
-<summary>Using docker</summary> ```json "mcpServers": { "docy": { "command": "docker", "args": ["run", "-i", "--rm", "oborchers/mcp-server-docy:latest"], "env":
@@ -196,1 +194,0 @@
-<summary>Using Docker</summary> ```json { "mcp": { "servers": { "docy": { "command": "docker", "args": ["run", "-i", "--rm", "oborchers/mcp-server-docy:latest"]

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.5.1. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: mseep-mcp-server-docy: Collapsed <details> block carrying instructions (KillerSkills verdict caution 55)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 55/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/mseep-mcp-server-docy/0.5.1

## Findings with a location
- `README.md:196` · Collapsed <details> block carrying instructions — README.md:196 · Collapsed <details> block carrying instructions
- `README.md:136` · Collapsed <details> block carrying instructions — README.md:136 · Collapsed <details> block carrying instructions
- `README.md:40` · Instructs the agent to modify its persistent memory or instruction files — README.md:40 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

## Proposed change
The attached patch removes the 3 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._