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 7 caught lines
Download .patchdiff --git a/references/AGENTS_TEMPLATE.md b/references/AGENTS_TEMPLATE.md --- a/references/AGENTS_TEMPLATE.md +++ b/references/AGENTS_TEMPLATE.md @@ -30,1 +30,0 @@ -- You can **read, edit, and update** MEMORY.md freely in main sessions @@ -32,1 +31,0 @@ -- Over time, review your daily files and update MEMORY.md with what's worth keeping @@ -65,1 +63,0 @@ -3. Update `MEMORY.md` with distilled learnings diff --git a/SKILL_v0.md b/SKILL_v0.md --- a/SKILL_v0.md +++ b/SKILL_v0.md @@ -38,1 +38,0 @@ -…# Step 2: Copy the AGENTS.md template Read `references/AGENTS_TEMPLATE.md` and write it to the agent's workspace as `AGENTS.md`. Adapt the heartbeat section to the agent's domain if needed (e.g., a CFO agen… diff --git a/skill-card.md b/skill-card.md --- a/skill-card.md +++ b/skill-card.md @@ -27,1 +27,0 @@ -Mitigation: Install only in the intended workspace after reviewing the AGENTS.md template and deciding which memory files the agent may read and update. diff --git a/SKILL.md b/SKILL.md --- a/SKILL.md +++ b/SKILL.md @@ -26,1 +26,0 @@ -# (read references/AGENTS_TEMPLATE.md, adapt, write to workspace/AGENTS.md) @@ -77,1 +76,0 @@ -Read `references/AGENTS_TEMPLATE.md` and write it to the agent's workspace as `AGENTS.md`.
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.2.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: agent-memory-setup-qmd: Instructs the agent to modify its persistent memory or instruction files (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/agent-memory-setup-qmd/1.2.0 ## Findings with a location - `references/AGENTS_TEMPLATE.md:65` · Instructs the agent to modify its persistent memory or instruction files — references/AGENTS_TEMPLATE.md:65 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `SKILL_v0.md:38` · Instructs the agent to modify its persistent memory or instruction files — SKILL_v0.md:38 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `skill-card.md:27` · Instructs the agent to modify its persistent memory or instruction files — skill-card.md:27 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `references/AGENTS_TEMPLATE.md:30` · Instructs the agent to modify its persistent memory or instruction files — references/AGENTS_TEMPLATE.md:30 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `SKILL.md:26` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:26 · Instructs the agent to modify its persistent memory or instruction files - `references/AGENTS_TEMPLATE.md:32` · Instructs the agent to modify its persistent memory or instruction files — references/AGENTS_TEMPLATE.md:32 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `SKILL.md:77` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:77 · Instructs the agent to modify its persistent memory or instruction files ## Proposed change The attached patch removes the 7 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 nichochar/openclaw --clone && cd openclaw curl -s https://killerskills.ai/skills/clawhub/agent-memory-setup-qmd/1.2.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.2.0 && git commit -am "agent-memory-setup-qmd: Instructs the agent to modify its persistent memory or instruction files" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/agent-memory-setup-qmd/1.2.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.