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. 61 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/STRUCTURE.md b/STRUCTURE.md --- a/STRUCTURE.md +++ b/STRUCTURE.md @@ -79,1 +79,0 @@ -5. **Configure:** Edit USER.md, TOOLS.md, AGENTS.md (Section 6) diff --git a/BOOTSTRAP.md b/BOOTSTRAP.md --- a/BOOTSTRAP.md +++ b/BOOTSTRAP.md @@ -344,1 +344,0 @@ -### 5.4 Update AGENTS.md @@ -346,1 +345,0 @@ -Add your VC-specific instructions. See `templates/AGENTS.md.example` for a full template. diff --git a/QUICKSTART.md b/QUICKSTART.md --- a/QUICKSTART.md +++ b/QUICKSTART.md @@ -118,1 +118,0 @@ -# Add to AGENTS.md (append to existing file)
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: clawdbot-for-vcs: Instructs the agent to modify its persistent memory or instruction files (KillerSkills verdict caution 61)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 61/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/clawdbot-for-vcs/1.0.0 ## Findings with a location - `STRUCTURE.md:79` · Instructs the agent to modify its persistent memory or instruction files — STRUCTURE.md:79 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `BOOTSTRAP.md:346` · Instructs the agent to modify its persistent memory or instruction files — BOOTSTRAP.md:346 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `QUICKSTART.md:118` · Instructs the agent to modify its persistent memory or instruction files — QUICKSTART.md:118 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `BOOTSTRAP.md:344` · Instructs the agent to modify its persistent memory or instruction files — BOOTSTRAP.md:344 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file ## Proposed change The attached patch removes the 4 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 martynsmith/gog --clone && cd gog curl -s https://killerskills.ai/skills/clawhub/clawdbot-for-vcs/1.0.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.0 && git commit -am "clawdbot-for-vcs: Instructs the agent to modify its persistent memory or instruction files" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/clawdbot-for-vcs/1.0.0/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.