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. 64 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 9 caught lines
Download .patchdiff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -20,1 +20,0 @@
-| `coder` | 👨💻 | 代码工匠 | 编码、调试、测试、重构 | read, write, edit, exec, process |
@@ -34,1 +33,0 @@
-| 👨💻 coder | 写出优雅高效的程序 | 先理解再动手、简单优于复杂、可读性优先 |
@@ -82,1 +80,0 @@
-| 写代码、修bug、脚本 | 👨💻 coder | 可执行 shell 命令 |
@@ -188,1 +185,0 @@
-├── 👨💻 coder
@@ -297,1 +293,0 @@
-├── coder/ # 👨💻 程序员
diff --git a/scripts/agent_manager.py b/scripts/agent_manager.py
--- a/scripts/agent_manager.py
+++ b/scripts/agent_manager.py
@@ -52,1 +52,0 @@
-"emoji": "👨💻",
diff --git a/scripts/init_agents.py b/scripts/init_agents.py
--- a/scripts/init_agents.py
+++ b/scripts/init_agents.py
@@ -57,1 +57,0 @@
-"emoji": "👨💻",
@@ -218,1 +217,0 @@
-f.write(f"""# AGENTS.md - {agent_info['name']} {agent_info['emoji']}
diff --git a/references/chj-private-config-template.json b/references/chj-private-config-template.json
--- a/references/chj-private-config-template.json
+++ b/references/chj-private-config-template.json
@@ -44,1 +44,0 @@
-"identity": { "name": "程序员", "emoji": "👨💻" },
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.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: lx-agent-swarm: Hidden zero-width characters detected (KillerSkills verdict caution 64)
## 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 64/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/lx-agent-swarm/1.0.0 ## Findings with a location - `SKILL.md:20` · Hidden zero-width characters detected — SKILL.md:20 · Hidden zero-width characters detected — may conceal content - `SKILL.md:297` · Hidden zero-width characters detected — SKILL.md:297 · Hidden zero-width characters detected — may conceal content - `SKILL.md:82` · Hidden zero-width characters detected — SKILL.md:82 · Hidden zero-width characters detected — may conceal content - `SKILL.md:34` · Hidden zero-width characters detected — SKILL.md:34 · Hidden zero-width characters detected — may conceal content - `SKILL.md:188` · Hidden zero-width characters detected — SKILL.md:188 · Hidden zero-width characters detected — may conceal content - `scripts/agent_manager.py:52` · Hidden zero-width characters detected — scripts/agent_manager.py:52 · Hidden zero-width characters detected — may conceal content - `scripts/init_agents.py:218` · Instructs the agent to modify its persistent memory or instruction files — scripts/init_agents.py:218 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `references/chj-private-config-template.json:44` · Hidden zero-width characters detected — references/chj-private-config-template.json:44 · Hidden zero-width characters detected — may conceal content - `scripts/init_agents.py:57` · Hidden zero-width characters detected — scripts/init_agents.py:57 · Hidden zero-width characters detected — may conceal content ## Proposed change The attached patch removes the 9 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._
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.