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. 69 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 5 caught lines
Download .patchdiff --git a/templates/AGENTS.md b/templates/AGENTS.md --- a/templates/AGENTS.md +++ b/templates/AGENTS.md @@ -55,1 +55,0 @@ -- You can **read, edit, and update** MEMORY.md freely in main sessions @@ -58,1 +57,0 @@ -- Over time, review your daily files and update MEMORY.md with what's worth keeping @@ -65,1 +63,0 @@ -- When you learn a lesson → update AGENTS.md, TOOLS.md, or the relevant skill @@ -213,1 +210,0 @@ -- **Review and update MEMORY.md** (see below) @@ -221,1 +217,0 @@ -3. Update `MEMORY.md` with distilled learnings
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: sagasmith: Instructs the agent to modify its persistent memory or instruction files (KillerSkills verdict caution 69)
## 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 69/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/sagasmith/1.0.2 ## Findings with a location - `templates/AGENTS.md:213` · Instructs the agent to modify its persistent memory or instruction files — templates/AGENTS.md:213 · Instructs the agent to modify its persistent memory or instruction files - `templates/AGENTS.md:221` · Instructs the agent to modify its persistent memory or instruction files — templates/AGENTS.md:221 · Instructs the agent to modify its persistent memory or instruction files - `templates/AGENTS.md:55` · Instructs the agent to modify its persistent memory or instruction files — templates/AGENTS.md:55 · Instructs the agent to modify its persistent memory or instruction files - `templates/AGENTS.md:65` · Instructs the agent to modify its persistent memory or instruction files — templates/AGENTS.md:65 · Instructs the agent to modify its persistent memory or instruction files - `templates/AGENTS.md:58` · Instructs the agent to modify its persistent memory or instruction files — templates/AGENTS.md:58 · Instructs the agent to modify its persistent memory or instruction files ## Proposed change The attached patch removes the 5 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 dajiaohuang/SagaSmith-skills --clone && cd SagaSmith-skills curl -s https://killerskills.ai/skills/clawhub/sagasmith/1.0.2/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.2 && git commit -am "sagasmith: Instructs the agent to modify its persistent memory or instruction files" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/sagasmith/1.0.2/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.