Propose a patch

Evidence

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

diff --git a/dist/index.js b/dist/index.js
--- a/dist/index.js
+++ b/dist/index.js
@@ -4,1 +4,0 @@
-…not read ${resolved} (${code})`)}let parsed;try{parsed=JSON.parse(raw.replace(/^ /,""))}catch{throw new Error(`--secrets-file: ${resolved} is not valid JSON`)}le…
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -318,1 +318,0 @@
-<summary><strong>Claude Code</strong></summary> Run the following command. See [Claude Code MCP docs](https://docs.anthropic.com/en/docs/claude-code/mcp) for mo
@@ -558,1 +557,0 @@
-<summary><strong>Smithery</strong></summary> Run the following command. You can find your Smithery API key [here](https://smithery.ai/account/api-keys). See the

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.53.0. 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: devtools: Hidden zero-width characters detected (KillerSkills verdict caution 74)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/devtools/0.53.0

## Findings with a location
- `dist/index.js:4` · Hidden zero-width characters detected — dist/index.js:4 · Hidden zero-width characters detected — may conceal content
- `README.md:318` · Collapsed <details> block carrying instructions — README.md:318 · Collapsed <details> block carrying instructions
- `README.md:558` · Collapsed <details> block carrying instructions — README.md:558 · Collapsed <details> block carrying instructions

## 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._