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. 65 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/references/cpn-xml-template.md b/references/cpn-xml-template.md --- a/references/cpn-xml-template.md +++ b/references/cpn-xml-template.md @@ -58,1 +58,0 @@ -库存资源库所(初始有 token,否则扣减变迁死锁) @@ -77,1 +76,0 @@ -DEP4: arc_sequence — 库存链内顺序,token 自然流动 @@ -106,1 +104,0 @@ -DEP4: fusion_place — 与 PAGE1.P2 共享 token,库存充足才能备餐 @@ -127,1 +124,0 @@ -DEP1: arc_sequence — 接单→备餐,token 流动自然表达顺序
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.3. 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: cpn-modeling: HTML comment carrying imperative instructions to the agent (KillerSkills verdict caution 65)
## 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 65/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/cpn-modeling/1.0.3 ## Findings with a location - `references/cpn-xml-template.md:77` · HTML comment carrying imperative instructions to the agent — references/cpn-xml-template.md:77 · HTML comment carrying imperative instructions to the agent - `references/cpn-xml-template.md:58` · HTML comment carrying imperative instructions to the agent — references/cpn-xml-template.md:58 · HTML comment carrying imperative instructions to the agent - `references/cpn-xml-template.md:127` · HTML comment carrying imperative instructions to the agent — references/cpn-xml-template.md:127 · HTML comment carrying imperative instructions to the agent - `references/cpn-xml-template.md:106` · HTML comment carrying imperative instructions to the agent — references/cpn-xml-template.md:106 · HTML comment carrying imperative instructions to the agent ## 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 theosunny/cpn-modeling-skill --clone && cd cpn-modeling-skill curl -s https://killerskills.ai/skills/clawhub/cpn-modeling/1.0.3/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.3 && git commit -am "cpn-modeling: HTML comment carrying imperative instructions to the agent" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/cpn-modeling/1.0.3/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.