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
@@ -32,1 +32,0 @@
-<summary>📖 如何获取 Token？</summary> 1. 访问 https://gitcode.com/setting/token-classic 2. 点击"生成新令牌" 3. 选择权限：`api`, `write_repository` 4. 复制生成的 Token
diff --git a/SETUP_GUIDE.md b/SETUP_GUIDE.md
--- a/SETUP_GUIDE.md
+++ b/SETUP_GUIDE.md
@@ -20,1 +20,0 @@
-<summary>🔑 获取 Token</summary> 1. 访问 https://gitcode.com/setting/token-classic 2. 点击"生成新令牌" 3. 选择权限：`api`, `write_repository` 4. 复制生成的 Token

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

## 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 68/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/cann-review/4.2.0

## Findings with a location
- `README.md:32` · Collapsed <details> block carrying instructions — README.md:32 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file
- `SETUP_GUIDE.md:20` · Collapsed <details> block carrying instructions — SETUP_GUIDE.md:20 · Collapsed <details> block carrying instructions · informational: not an instruction file · informational: not an instruction file

## Proposed change
The attached patch removes the 2 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._