Propose a patch
A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 78 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 7 caught lines
Download .patchdiff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -202,1 +202,0 @@
-<summary><strong>Claude Code</strong></summary> Add via CLI: ```bash claude mcp add manager --env MANAGER_API_URL=http://127.0.0.1:55667/api2 --env MANAGER_API_
@@ -230,1 +229,0 @@
-<summary><strong>VS Code / GitHub Copilot</strong></summary> Create [`.vscode/mcp.json`](.vscode/mcp.json) in the project root: ```json { "servers": { "manager"
@@ -273,1 +271,0 @@
-<summary><strong>Windsurf</strong></summary> Edit `~/.codeium/windsurf/mcp_config.json` (macOS/Linux) or the Windsurf MCP settings UI: ```json { "mcpServers": {
@@ -297,1 +294,0 @@
-<summary><strong>Zed</strong></summary> Add under `context_servers` in Zed `settings.json` (Agent Panel → settings also works): ```json { "context_servers": { "
@@ -319,1 +315,0 @@
-<summary><strong>Cline</strong></summary> Edit the Cline MCP settings file (`cline_mcp_settings.json` via the Cline MCP UI): ```json { "mcpServers": { "manager"
@@ -341,1 +336,0 @@
-<summary><strong>Continue</strong></summary> In `.continue/config.yaml`: ```yaml mcpServers: - name: manager command: uvx args: - manager-mcp env: MANAGER_API_U
@@ -359,1 +353,0 @@
-<summary><strong>Generic / any stdio MCP host</strong></summary> Any host that can spawn a stdio MCP server: | Field | Value | |-------|-------| | Command | `uv
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.6. 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: manager-mcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 78)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 78/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/manager-mcp/0.2.6 ## Findings with a location - `README.md:359` · Collapsed <details> block carrying instructions — README.md:359 · Collapsed <details> block carrying instructions - `README.md:202` · Collapsed <details> block carrying instructions — README.md:202 · Collapsed <details> block carrying instructions - `README.md:341` · Collapsed <details> block carrying instructions — README.md:341 · Collapsed <details> block carrying instructions - `README.md:273` · Collapsed <details> block carrying instructions — README.md:273 · Collapsed <details> block carrying instructions - `README.md:230` · Collapsed <details> block carrying instructions — README.md:230 · Collapsed <details> block carrying instructions - `README.md:319` · Collapsed <details> block carrying instructions — README.md:319 · Collapsed <details> block carrying instructions - `README.md:297` · Collapsed <details> block carrying instructions — README.md:297 · Collapsed <details> block carrying instructions ## Proposed change The attached patch removes the 7 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._
# or from a terminal, under your own account: gh repo fork flumpiey/manager-mcp --clone && cd manager-mcp curl -s https://killerskills.ai/skills/pypi/manager-mcp/0.2.6/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.2.6 && git commit -am "manager-mcp: Collapsed <details> block carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/manager-mcp/0.2.6/patch.md)
We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.