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. 72 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 52 caught lines
Download .patchdiff --git a/SKILL.md b/SKILL.md --- a/SKILL.md +++ b/SKILL.md @@ -140,1 +140,0 @@ -<context> @@ -143,1 +142,0 @@ -</context> @@ -207,1 +205,0 @@ -- `<context>`: Add exact file paths (verified with `ls`), what OTHER agents handle (boundary awareness) diff --git a/docs/references/api-template.md b/docs/references/api-template.md --- a/docs/references/api-template.md +++ b/docs/references/api-template.md @@ -12,1 +12,0 @@ -<context> @@ -17,1 +16,0 @@ -</context> @@ -82,1 +80,0 @@ -<context> @@ -87,1 +84,0 @@ -</context> diff --git a/docs/references/feature-template.md b/docs/references/feature-template.md --- a/docs/references/feature-template.md +++ b/docs/references/feature-template.md @@ -12,1 +12,0 @@ -<context> @@ -17,1 +16,0 @@ -</context> @@ -73,1 +71,0 @@ -<context> @@ -78,1 +75,0 @@ -</context> diff --git a/docs/references/bugfix-template.md b/docs/references/bugfix-template.md --- a/docs/references/bugfix-template.md +++ b/docs/references/bugfix-template.md @@ -12,1 +12,0 @@ -<context> @@ -17,1 +16,0 @@ -</context> @@ -88,1 +86,0 @@ -<context> @@ -93,1 +90,0 @@ -</context> diff --git a/docs/references/content-template.md b/docs/references/content-template.md --- a/docs/references/content-template.md +++ b/docs/references/content-template.md @@ -10,1 +10,0 @@ -<context> @@ -15,1 +14,0 @@ -</context> @@ -65,1 +63,0 @@ -<context> @@ -70,1 +67,0 @@ -</context> diff --git a/docs/references/docs-template.md b/docs/references/docs-template.md --- a/docs/references/docs-template.md +++ b/docs/references/docs-template.md @@ -12,1 +12,0 @@ -<context> @@ -17,1 +16,0 @@ -</context> @@ -88,1 +86,0 @@ -<context> @@ -93,1 +90,0 @@ -</context> diff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -137,1 +137,0 @@ -<context> @@ -142,1 +141,0 @@ -</context> @@ -239,1 +237,0 @@ -<context> @@ -244,1 +241,0 @@ -</context> @@ -294,1 +290,0 @@ -<context> diff --git a/docs/references/refactor-template.md b/docs/references/refactor-template.md --- a/docs/references/refactor-template.md +++ b/docs/references/refactor-template.md @@ -12,1 +12,0 @@ -<context> @@ -17,1 +16,0 @@ -</context> @@ -87,1 +85,0 @@ -<context> @@ -92,1 +89,0 @@ -</context> diff --git a/docs/references/swarm-template.md b/docs/references/swarm-template.md --- a/docs/references/swarm-template.md +++ b/docs/references/swarm-template.md @@ -12,1 +12,0 @@ -<context> @@ -17,1 +16,0 @@ -</context> @@ -93,1 +91,0 @@ -<context> @@ -98,1 +95,0 @@ -</context> diff --git a/docs/references/testing-template.md b/docs/references/testing-template.md --- a/docs/references/testing-template.md +++ b/docs/references/testing-template.md @@ -12,1 +12,0 @@ -<context> @@ -17,1 +16,0 @@ -</context> @@ -81,1 +79,0 @@ -<context> @@ -86,1 +83,0 @@ -</context> diff --git a/docs/references/ui-template.md b/docs/references/ui-template.md --- a/docs/references/ui-template.md +++ b/docs/references/ui-template.md @@ -12,1 +12,0 @@ -<context> @@ -17,1 +16,0 @@ -</context> @@ -83,1 +81,0 @@ -<context> @@ -88,1 +85,0 @@ -</context> diff --git a/docs/references/research-template.md b/docs/references/research-template.md --- a/docs/references/research-template.md +++ b/docs/references/research-template.md @@ -12,1 +12,0 @@ -<context> @@ -17,1 +16,0 @@ -</context> @@ -105,1 +103,0 @@ -<context> @@ -110,1 +107,0 @@ -</context> diff --git a/docs/references/security-template.md b/docs/references/security-template.md --- a/docs/references/security-template.md +++ b/docs/references/security-template.md @@ -12,1 +12,0 @@ -<context> @@ -18,1 +17,0 @@ -</context> @@ -84,1 +82,0 @@ -<context> @@ -90,1 +87,0 @@ -</context>
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 7.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: reprompter: Fake instruction boundary tag (KillerSkills verdict caution 72)
## 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 72/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/reprompter/7.0.0 ## Findings with a location - `SKILL.md:207` · Fake instruction boundary tag — SKILL.md:207 · Fake instruction boundary tag - `SKILL.md:143` · Fake instruction boundary tag — SKILL.md:143 · Fake instruction boundary tag - `SKILL.md:140` · Fake instruction boundary tag — SKILL.md:140 · Fake instruction boundary tag - `docs/references/api-template.md:17` · Fake instruction boundary tag — docs/references/api-template.md:17 · Fake instruction boundary tag · informational: not an instruction file - `docs/references/feature-template.md:17` · Fake instruction boundary tag — docs/references/feature-template.md:17 · Fake instruction boundary tag · informational: not an instruction file - `docs/references/bugfix-template.md:88` · Fake instruction boundary tag — docs/references/bugfix-template.md:88 · Fake instruction boundary tag · informational: not an instruction file - `docs/references/content-template.md:65` · Fake instruction boundary tag — docs/references/content-template.md:65 · Fake instruction boundary tag · informational: not an instruction file - `docs/references/feature-template.md:73` · Fake instruction boundary tag — docs/references/feature-template.md:73 · Fake instruction boundary tag · informational: not an instruction file - `docs/references/bugfix-template.md:17` · Fake instruction boundary tag — docs/references/bugfix-template.md:17 · Fake instruction boundary tag · informational: not an instruction file - `docs/references/docs-template.md:12` · Fake instruction boundary tag — docs/references/docs-template.md:12 · Fake instruction boundary tag · informational: not an instruction file - `docs/references/bugfix-template.md:93` · Fake instruction boundary tag — docs/references/bugfix-template.md:93 · Fake instruction boundary tag · informational: not an instruction file - `docs/references/feature-template.md:12` · Fake instruction boundary tag — docs/references/feature-template.md:12 · Fake instruction boundary tag · informational: not an instruction file ## Proposed change The attached patch removes the 52 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 aytuncyildizli/reprompter --clone && cd reprompter curl -s https://killerskills.ai/skills/clawhub/reprompter/7.0.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/7.0.0 && git commit -am "reprompter: Fake instruction boundary tag" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/reprompter/7.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.