Propose a patch

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

diff --git a/skill_service/vendor/book_to_skill/utils.py b/skill_service/vendor/book_to_skill/utils.py
--- a/skill_service/vendor/book_to_skill/utils.py
+++ b/skill_service/vendor/book_to_skill/utils.py
@@ -258,1 +258,0 @@
-#     so "فصل اولویت‌ها" / "فصل اولیه" are not read as chapter 1;
@@ -286,1 +285,0 @@
-# Fused "بیستم" only — "بیست ام" / "بیست‌ام" are not common spellings
@@ -287,1 +285,0 @@
-# (unlike "سی ام" / "سی‌ام" for 30), so they stay unmapped on purpose.
@@ -290,1 +287,0 @@
-m["سی‌ام"] = 30  # ZWNJ spelling common in Persian typography
diff --git a/skill_service/vendor/docs/how-it-works.md b/skill_service/vendor/docs/how-it-works.md
--- a/skill_service/vendor/docs/how-it-works.md
+++ b/skill_service/vendor/docs/how-it-works.md
@@ -73,1 +73,0 @@
-<summary>Design principles (click to expand)</summary> 1. **Density over completeness** — a 1,000-token summary beats a 10,000-token excerpt 2. **Practitioner v
diff --git a/skill_service/vendor/tools/validate_skill.py b/skill_service/vendor/tools/validate_skill.py
--- a/skill_service/vendor/tools/validate_skill.py
+++ b/skill_service/vendor/tools/validate_skill.py
@@ -152,1 +152,0 @@
-# leading  makes text.startswith("---") false and frontmatter is missed.
diff --git a/skill_service/vendor/SKILL.md b/skill_service/vendor/SKILL.md
--- a/skill_service/vendor/SKILL.md
+++ b/skill_service/vendor/SKILL.md
@@ -391,1 +391,0 @@
-Reproduce or reconstruct one concrete example the author works through: a sample document, a dialogue, a filled-in template, a before/after, or a decision walke

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.3.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: mineru-book-mcp: Hidden zero-width characters detected (KillerSkills verdict caution 66)

## 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 66/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/mineru-book-mcp/0.3.0

## Findings with a location
- `skill_service/vendor/book_to_skill/utils.py:258` · Hidden zero-width characters detected — skill_service/vendor/book_to_skill/utils.py:258 · Hidden zero-width characters detected — may conceal content
- `skill_service/vendor/book_to_skill/utils.py:290` · Hidden zero-width characters detected — skill_service/vendor/book_to_skill/utils.py:290 · Hidden zero-width characters detected — may conceal content
- `skill_service/vendor/docs/how-it-works.md:73` · Collapsed <details> block carrying instructions — skill_service/vendor/docs/how-it-works.md:73 · Collapsed <details> block carrying instructions
- `skill_service/vendor/book_to_skill/utils.py:286` · Hidden zero-width characters detected — skill_service/vendor/book_to_skill/utils.py:286 · Hidden zero-width characters detected — may conceal content
- `skill_service/vendor/book_to_skill/utils.py:287` · Hidden zero-width characters detected — skill_service/vendor/book_to_skill/utils.py:287 · Hidden zero-width characters detected — may conceal content
- `skill_service/vendor/tools/validate_skill.py:152` · Hidden zero-width characters detected — skill_service/vendor/tools/validate_skill.py:152 · Hidden zero-width characters detected — may conceal content
- `skill_service/vendor/SKILL.md:391` · HTML comment carrying imperative instructions to the agent — skill_service/vendor/SKILL.md:391 · HTML comment carrying imperative instructions to the agent

## 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._