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
@@ -93,1 +93,0 @@
-<summary><b>Option 1: Install through npx ⭐ Auto-Updates (Requires Node.js)</b></summary> Just run this in terminal: ``` npx @wonderwhy-er/desktop-commander@lat
@@ -118,1 +117,0 @@
-<summary><b>Option 2: Using bash script installer (macOS) ⭐ Auto-Updates (Installs Node.js if needed)</b></summary> ``` curl -fsSL https://raw.githubusercontent
@@ -146,1 +144,0 @@
-<summary><b>Option 4: Add to claude_desktop_config manually ⭐ Auto-Updates (Requires Node.js)</b></summary> Add this entry to your claude_desktop_config.json: -
@@ -176,1 +173,0 @@
-<summary><b>Option 5: Checkout locally ❌ Manual Updates (Requires Node.js)</b></summary> ```bash git clone https://github.com/wonderwhy-er/DesktopCommanderMCP.g
@@ -215,1 +211,0 @@
-<summary>Manual Docker Configuration</summary> **Basic setup (no file access):** ```json { "mcpServers": { "desktop-commander-in-docker": { "command": "docker",
@@ -1076,1 +1071,0 @@
-It's a life saver! I paid Claude + Cursor currently which I always feel it's kind of duplicated. This solves the problem ultimately. I am so happy. Thanks so mu
@@ -1084,1 +1078,0 @@
-Great! I just used Windsurf, bought license a week ago, for upgrading old fullstack socket project and it works many times good or ok but also many times runs a

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.3.2. 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: desktop-commander: Collapsed <details> block carrying instructions (KillerSkills verdict caution 64)

## 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 64/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/docker/desktop-commander/0.3.2

## Findings with a location
- `README.md:176` · Collapsed <details> block carrying instructions — README.md:176 · Collapsed <details> block carrying instructions
- `README.md:118` · Collapsed <details> block carrying instructions — README.md:118 · Collapsed <details> block carrying instructions
- `README.md:146` · Collapsed <details> block carrying instructions — README.md:146 · Collapsed <details> block carrying instructions
- `README.md:93` · Collapsed <details> block carrying instructions — README.md:93 · Collapsed <details> block carrying instructions
- `README.md:215` · Collapsed <details> block carrying instructions — README.md:215 · Collapsed <details> block carrying instructions
- `README.md:1084` · Image alt text carrying instructions — README.md:1084 · Image alt text carrying instructions
- `README.md:1076` · Image alt text carrying instructions — README.md:1076 · Image alt text 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._