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. 53 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 10 caught lines
Download .patchdiff --git a/mcp-server/server.py b/mcp-server/server.py
--- a/mcp-server/server.py
+++ b/mcp-server/server.py
@@ -1,1 +1,0 @@
-#!/usr/bin/env python3
diff --git a/vault-templates/CORE_MEMORY.template.md b/vault-templates/CORE_MEMORY.template.md
--- a/vault-templates/CORE_MEMORY.template.md
+++ b/vault-templates/CORE_MEMORY.template.md
@@ -131,1 +131,0 @@
-**Update CORE_MEMORY.md when:**
diff --git a/tools/reconcile_memory.py b/tools/reconcile_memory.py
--- a/tools/reconcile_memory.py
+++ b/tools/reconcile_memory.py
@@ -529,1 +529,0 @@
-rlog(f"Failed to write CORE_MEMORY.md: {e}", "ERROR")
diff --git a/SETUP_AI.md b/SETUP_AI.md
--- a/SETUP_AI.md
+++ b/SETUP_AI.md
@@ -72,1 +72,0 @@
-Read `vault-templates/CORE_MEMORY.template.md`. Apply the same substitutions as 1.2 plus any additional project/context detail the user provided. Write to `$VAULT\CORE_MEMORY.md`.
@@ -378,1 +377,0 @@
-Write-Host "CORE_MEMORY.md:" (Test-Path "$v\CORE_MEMORY.md")
diff --git a/engine/openclaw.template.json b/engine/openclaw.template.json
--- a/engine/openclaw.template.json
+++ b/engine/openclaw.template.json
@@ -87,1 +87,0 @@
-…es to C:\\YOUR_VAULT_PATH\\workspace\\memory\\YYYY-MM-DD.md in Markdown format. Update C:\\YOUR_VAULT_PATH\\CORE_MEMORY.md if project state has changed. Reply with NO_REPLY if nothing to store.", …
diff --git a/vault-templates/BOOT_SEQUENCE.md b/vault-templates/BOOT_SEQUENCE.md
--- a/vault-templates/BOOT_SEQUENCE.md
+++ b/vault-templates/BOOT_SEQUENCE.md
@@ -86,1 +86,0 @@
-"Write any lasting notes to your Vault memory file. Update CORE_MEMORY.md if
diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md
--- a/docs/ARCHITECTURE.md
+++ b/docs/ARCHITECTURE.md
@@ -99,1 +99,0 @@
-"prompt": "Write any lasting notes to YOUR_VAULT/memory/YYYY-MM-DD.md. Update CORE_MEMORY.md if project state has changed. Reply with NO_REPLY if nothing to store.",
diff --git a/docs/SWARM.md b/docs/SWARM.md
--- a/docs/SWARM.md
+++ b/docs/SWARM.md
@@ -158,1 +158,0 @@
-**5. Tell Adam about it** — update `CORE_MEMORY.md` with the new agent's capabilities
diff --git a/index.html b/index.html
--- a/index.html
+++ b/index.html
@@ -232,1 +232,0 @@
-…div><div class="timeline-event">Layer 1 emerges</div><div class="timeline-desc">Write everything down in files, make the AI read them. SOUL.md and CORE_MEMORY.md created. Session coherence improved immediately.</div></div> <div class="…
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: adam-framework: Hidden zero-width characters detected (KillerSkills verdict caution 53)
## 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 53/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/adam-framework/1.0.1 ## Findings with a location - `mcp-server/server.py:1` · Hidden zero-width characters detected — mcp-server/server.py:1 · Hidden zero-width characters detected — may conceal content - `vault-templates/CORE_MEMORY.template.md:131` · Instructs the agent to modify its persistent memory or instruction files — vault-templates/CORE_MEMORY.template.md:131 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `tools/reconcile_memory.py:529` · Instructs the agent to modify its persistent memory or instruction files — tools/reconcile_memory.py:529 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `SETUP_AI.md:378` · Instructs the agent to modify its persistent memory or instruction files — SETUP_AI.md:378 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `SETUP_AI.md:72` · Instructs the agent to modify its persistent memory or instruction files — SETUP_AI.md:72 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `engine/openclaw.template.json:87` · Instructs the agent to modify its persistent memory or instruction files — engine/openclaw.template.json:87 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `vault-templates/BOOT_SEQUENCE.md:86` · Instructs the agent to modify its persistent memory or instruction files — vault-templates/BOOT_SEQUENCE.md:86 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `docs/ARCHITECTURE.md:99` · Instructs the agent to modify its persistent memory or instruction files — docs/ARCHITECTURE.md:99 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `docs/SWARM.md:158` · Instructs the agent to modify its persistent memory or instruction files — docs/SWARM.md:158 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `index.html:232` · Instructs the agent to modify its persistent memory or instruction files — index.html:232 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file ## Proposed change The attached patch removes the 10 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 strangeadvancedmarketing/Adam --clone && cd Adam curl -s https://killerskills.ai/skills/clawhub/adam-framework/1.0.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.0.1 && git commit -am "adam-framework: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/adam-framework/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.