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. 56 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 1 caught line
Download .patchdiff --git a/CHANGELOG.md b/CHANGELOG.md --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3013,1 +3013,0 @@ -…达风格、不复用样本事实。理由：样本可能含过时信息。 - **P1-D 本地用户记忆**：新增 `scripts/memory_manager.py`，支持 `add/list/load/prune/clear`，写入 `~/.workbuddy/ct-advisor-memory.json`（**刻意避开** `MEMORY.md` 以免冲突）；默认 **TTL 90 天**（过期由 `prune` 清理）；`add` 非交互模式强制 `--confirm`、`clear` 强制 `--…
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.3.42. 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: ct-advisor: Instructs the agent to modify its persistent memory or instruction files (KillerSkills verdict caution 56)
## 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 56/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/ct-advisor/1.3.42 ## Findings with a location - `CHANGELOG.md:3013` · Instructs the agent to modify its persistent memory or instruction files — CHANGELOG.md:3013 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file ## Proposed change The attached patch removes the 1 line 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 medstatstar/ct-advisor --clone && cd ct-advisor curl -s https://killerskills.ai/skills/clawhub/ct-advisor/1.3.42/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.3.42 && git commit -am "ct-advisor: Instructs the agent to modify its persistent memory or instruction files" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/ct-advisor/1.3.42/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.