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. 61 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/deadclaw/docs/iphone-shortcut-guide.md b/deadclaw/docs/iphone-shortcut-guide.md --- a/deadclaw/docs/iphone-shortcut-guide.md +++ b/deadclaw/docs/iphone-shortcut-guide.md @@ -87,1 +87,0 @@ -SCREENSHOT_PLACEHOLDER: test-run-result.png diff --git a/docs/iphone-shortcut-guide.md b/docs/iphone-shortcut-guide.md --- a/docs/iphone-shortcut-guide.md +++ b/docs/iphone-shortcut-guide.md @@ -87,1 +87,0 @@ -SCREENSHOT_PLACEHOLDER: test-run-result.png diff --git a/deadclaw/ui/deadclaw-button.html b/deadclaw/ui/deadclaw-button.html --- a/deadclaw/ui/deadclaw-button.html +++ b/deadclaw/ui/deadclaw-button.html @@ -2,1 +2,0 @@ -DeadClaw — WebChat Kill Button Widget A persistent red button for the OpenClaw WebChat dashboard. When clicked, it calls kill.sh via OpenClaw's WebChat API hook diff --git a/ui/deadclaw-button.html b/ui/deadclaw-button.html --- a/ui/deadclaw-button.html +++ b/ui/deadclaw-button.html @@ -2,1 +2,0 @@ -DeadClaw — WebChat Kill Button Widget A persistent red button for the OpenClaw WebChat dashboard. When clicked, it calls kill.sh via OpenClaw's WebChat API hook
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.1. 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: deadclaw: HTML comment carrying imperative instructions to the agent (KillerSkills verdict caution 61)
## 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 61/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/deadclaw/1.0.1 ## Findings with a location - `deadclaw/docs/iphone-shortcut-guide.md:87` · HTML comment carrying imperative instructions to the agent — deadclaw/docs/iphone-shortcut-guide.md:87 · HTML comment carrying imperative instructions to the agent - `docs/iphone-shortcut-guide.md:87` · HTML comment carrying imperative instructions to the agent — docs/iphone-shortcut-guide.md:87 · HTML comment carrying imperative instructions to the agent - `deadclaw/ui/deadclaw-button.html:2` · HTML comment carrying imperative instructions to the agent — deadclaw/ui/deadclaw-button.html:2 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file - `ui/deadclaw-button.html:2` · HTML comment carrying imperative instructions to the agent — ui/deadclaw-button.html:2 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file ## Proposed change The attached patch removes the 4 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 Kintupercy/deadclaw --clone && cd deadclaw curl -s https://killerskills.ai/skills/clawhub/deadclaw/1.0.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.1 && git commit -am "deadclaw: HTML comment carrying imperative instructions to the agent" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/deadclaw/1.0.1/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.