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. 63 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 2 caught lines
Download .patchdiff --git a/skills/fallow/references/cli-reference.md b/skills/fallow/references/cli-reference.md --- a/skills/fallow/references/cli-reference.md +++ b/skills/fallow/references/cli-reference.md @@ -78,1 +78,0 @@ -fallow-ignore-file complexity diff --git a/skills/fallow/SKILL.md b/skills/fallow/SKILL.md --- a/skills/fallow/SKILL.md +++ b/skills/fallow/SKILL.md @@ -69,1 +69,0 @@ -Offer these choices: guard commits and PRs, baseline the existing backlog and clean by category, add AGENTS.md guidance, or keep as-is. Mutate only after consent. On decline, run `fallow init --declin
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.40.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: fallow: HTML comment carrying imperative instructions to the agent (KillerSkills verdict caution 63)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.5) and scored it **CAUTION 63/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/npm/fallow/3.40.0 ## Findings with a location - `skills/fallow/references/cli-reference.md:78` · HTML comment carrying imperative instructions to the agent — skills/fallow/references/cli-reference.md:78 · HTML comment carrying imperative instructions to the agent - `skills/fallow/SKILL.md:69` · Instructs the agent to modify its persistent memory or instruction files — skills/fallow/SKILL.md:69 · Instructs the agent to modify its persistent memory or instruction files ## 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._
# or from a terminal, under your own account: gh repo fork fallow-rs/fallow --clone && cd fallow curl -s https://killerskills.ai/skills/npm/fallow/3.40.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/3.40.0 && git commit -am "fallow: HTML comment carrying imperative instructions to the agent" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/fallow/3.40.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.