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. 70 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/SKILL.md b/SKILL.md --- a/SKILL.md +++ b/SKILL.md @@ -49,1 +49,0 @@ -After changes, update the workspace structure tree in `MEMORY.md` if one exists. @@ -55,1 +54,0 @@ -- **Promote WARM → HOT**: Add a summary line to `MEMORY.md` diff --git a/skill-card.md b/skill-card.md --- a/skill-card.md +++ b/skill-card.md @@ -51,1 +51,0 @@ -**Other Properties Related to Output:** [May include proposed or completed file cleanup, archive, rename, MEMORY.md update, and tier promotion or demotion details.] diff --git a/references/tier-rules.md b/references/tier-rules.md --- a/references/tier-rules.md +++ b/references/tier-rules.md @@ -13,1 +13,0 @@ -2. Add to the appropriate section in `MEMORY.md`
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: nightly-workspace-audit: Instructs the agent to modify its persistent memory or instruction files (KillerSkills verdict caution 70)
## 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 70/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/nightly-workspace-audit/1.0.0 ## Findings with a location - `SKILL.md:55` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:55 · Instructs the agent to modify its persistent memory or instruction files - `skill-card.md:51` · Instructs the agent to modify its persistent memory or instruction files — skill-card.md:51 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `references/tier-rules.md:13` · Instructs the agent to modify its persistent memory or instruction files — references/tier-rules.md:13 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `SKILL.md:49` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:49 · Instructs the agent to modify its persistent memory or instruction files ## 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._
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.