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. 55 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 2 caught lines
Download .patchdiff --git a/s2_kernel/rights/s2_family_rights.py b/s2_kernel/rights/s2_family_rights.py
--- a/s2_kernel/rights/s2_family_rights.py
+++ b/s2_kernel/rights/s2_family_rights.py
@@ -70,1 +70,0 @@
-self.logger.info(f"👨👩👧👦 成员注册成功: {nickname} ({relation})。请强制修改初始密码。")
diff --git a/s2_kernel/chronos/s2_garden_manager.py b/s2_kernel/chronos/s2_garden_manager.py
--- a/s2_kernel/chronos/s2_garden_manager.py
+++ b/s2_kernel/chronos/s2_garden_manager.py
@@ -142,1 +142,0 @@
-print("\n 👨🌾 今日需要您（或园丁）协助照料的室内植物：")
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.1.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: s2-space-agent-os-mothership: Hidden zero-width characters detected (KillerSkills verdict caution 55)
## 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 55/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/s2-space-agent-os-mothership/1.1.3 ## Findings with a location - `s2_kernel/rights/s2_family_rights.py:70` · Hidden zero-width characters detected — s2_kernel/rights/s2_family_rights.py:70 · Hidden zero-width characters detected — may conceal content - `s2_kernel/chronos/s2_garden_manager.py:142` · Hidden zero-width characters detected — s2_kernel/chronos/s2_garden_manager.py:142 · Hidden zero-width characters detected — may conceal content ## Proposed change The attached patch removes the 2 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 SpaceSQ/s2-os-core --clone && cd s2-os-core curl -s https://killerskills.ai/skills/clawhub/s2-space-agent-os-mothership/1.1.3/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.1.3 && git commit -am "s2-space-agent-os-mothership: Hidden zero-width characters detected" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/s2-space-agent-os-mothership/1.1.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.