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. 78 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 5 caught lines
Download .patchdiff --git a/modules/identity-and-voice-leaks.md b/modules/identity-and-voice-leaks.md --- a/modules/identity-and-voice-leaks.md +++ b/modules/identity-and-voice-leaks.md @@ -286,1 +286,0 @@ -slop-detector:ignore diff --git a/modules/anti-goals.md b/modules/anti-goals.md --- a/modules/anti-goals.md +++ b/modules/anti-goals.md @@ -287,1 +287,0 @@ -slop-detector:ignore-next-line vocabulary @@ -290,1 +289,0 @@ -slop-detector:ignore-block start @@ -292,1 +290,0 @@ -slop-detector:ignore-block end @@ -304,1 +301,0 @@ -slop-detector:ignore-next-line vocabulary reason: "comprehensive" is the documented test-suite name; renaming it breaks external references
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.9.19. 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: nm-scribe-slop-detector: HTML comment carrying imperative instructions to the agent (KillerSkills verdict caution 78)
## 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 78/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/nm-scribe-slop-detector/1.9.19 ## Findings with a location - `modules/identity-and-voice-leaks.md:286` · HTML comment carrying imperative instructions to the agent — modules/identity-and-voice-leaks.md:286 · HTML comment carrying imperative instructions to the agent - `modules/anti-goals.md:292` · HTML comment carrying imperative instructions to the agent — modules/anti-goals.md:292 · HTML comment carrying imperative instructions to the agent - `modules/anti-goals.md:304` · HTML comment carrying imperative instructions to the agent — modules/anti-goals.md:304 · HTML comment carrying imperative instructions to the agent - `modules/anti-goals.md:290` · HTML comment carrying imperative instructions to the agent — modules/anti-goals.md:290 · HTML comment carrying imperative instructions to the agent - `modules/anti-goals.md:287` · HTML comment carrying imperative instructions to the agent — modules/anti-goals.md:287 · HTML comment carrying imperative instructions to the agent ## Proposed change The attached patch removes the 5 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 athola/claude-night-market --clone && cd claude-night-market curl -s https://killerskills.ai/skills/clawhub/nm-scribe-slop-detector/1.9.19/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.9.19 && git commit -am "nm-scribe-slop-detector: HTML comment carrying imperative instructions to the agent" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/nm-scribe-slop-detector/1.9.19/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.