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. 79 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 2 caught lines
Download .patchdiff --git a/skill-sources/sandscape-assets/SKILL.md b/skill-sources/sandscape-assets/SKILL.md --- a/skill-sources/sandscape-assets/SKILL.md +++ b/skill-sources/sandscape-assets/SKILL.md @@ -48,1 +48,0 @@ -… ## Edit existing registered images Use `asset edit-image <asset_id> --prompt <instruction> --max-coins <authorized-ceiling> --json` when the output should become a new ve… diff --git a/dist/local/layout.js b/dist/local/layout.js --- a/dist/local/layout.js +++ b/dist/local/layout.js @@ -282,1 +282,0 @@ -* Write AGENTS.md as a POSIX symlink to CLAUDE.md, falling back to a small
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.3.0-beta.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: cli: Fake instruction boundary tag (KillerSkills verdict caution 79)
## 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 79/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/cli/0.3.0-beta.2 ## Findings with a location - `skill-sources/sandscape-assets/SKILL.md:48` · Fake instruction boundary tag — skill-sources/sandscape-assets/SKILL.md:48 · Fake instruction boundary tag - `dist/local/layout.js:282` · Instructs the agent to modify its persistent memory or instruction files — dist/local/layout.js:282 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file ## 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 snadeau123/sandscapeapp --clone && cd sandscapeapp curl -s https://killerskills.ai/skills/npm/cli/0.3.0-beta.2/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.3.0-beta.2 && git commit -am "cli: Fake instruction boundary tag" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/cli/0.3.0-beta.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.