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. 73 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 2 caught lines
Download .patchdiff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -767,1 +767,0 @@ -identity type `custom:<system>-agent` with the agent id as its value. diff --git a/scripts/build_demo.mjs b/scripts/build_demo.mjs --- a/scripts/build_demo.mjs +++ b/scripts/build_demo.mjs @@ -59,1 +59,0 @@ -<link href="https://fonts.googleapis.com/css2?family=Plus+Jakarta+Sans:wght@400;500;600;700&display=optional" rel="stylesheet" />
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.7.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: ghostpaw-affinity: Fake instruction boundary tag (KillerSkills verdict caution 73)
## 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 73/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/ghostpaw-affinity/0.7.2 ## Findings with a location - `README.md:767` · Fake instruction boundary tag — README.md:767 · Fake instruction boundary tag · informational: not an instruction file - `scripts/build_demo.mjs:59` · URL with embedded credentials — scripts/build_demo.mjs:59 · URL with embedded credentials — may be phishing or credential leaking ## 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 GhostPawJS/affinity --clone && cd affinity curl -s https://killerskills.ai/skills/glama/ghostpaw-affinity/0.7.2/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.7.2 && git commit -am "ghostpaw-affinity: Fake instruction boundary tag" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/ghostpaw-affinity/0.7.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.