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. 62 · Caution

Evidence

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

Diff · removes 3 caught lines

Download .patch

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -58,1 +58,0 @@
-<summary><b>Build from source</b></summary> ```bash # Prerequisites: mise (https://mise.jdx.dev), git. git clone https://github.com/mo-cmyk/mazarbul.git cd maza
diff --git a/.claude/skills/task-execution-protocol/SKILL.md b/.claude/skills/task-execution-protocol/SKILL.md
--- a/.claude/skills/task-execution-protocol/SKILL.md
+++ b/.claude/skills/task-execution-protocol/SKILL.md
@@ -85,1 +85,0 @@
-- User-facing change? Update the matching `agent-docs/*.md` and append to `agent-docs/mintlify-backlog.md` (AGENTS.md rule 11).
diff --git a/.claude/hooks/route-prompt.sh b/.claude/hooks/route-prompt.sh
--- a/.claude/hooks/route-prompt.sh
+++ b/.claude/hooks/route-prompt.sh
@@ -103,1 +103,0 @@
-# Boris Cherny: "After every correction, end with: Update CLAUDE.md so you

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of r1. 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: mazarbul: Collapsed <details> block carrying instructions (KillerSkills verdict caution 62)

## What the honeypot observed
KillerSkills ran **mazarbul@r1** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 62/100**. Summary: calls api.github.com only, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/mazarbul/r1

## Findings with a location
- `README.md:58` · Collapsed <details> block carrying instructions — README.md:58 · Collapsed <details> block carrying instructions
- `.claude/skills/task-execution-protocol/SKILL.md:85` · Instructs the agent to modify its persistent memory or instruction files — .claude/skills/task-execution-protocol/SKILL.md:85 · Instructs the agent to modify its persistent memory or instruction files
- `.claude/hooks/route-prompt.sh:103` · Instructs the agent to modify its persistent memory or instruction files — .claude/hooks/route-prompt.sh:103 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

## Proposed change
The attached patch removes the 3 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._

Open the issue on GitHub (mo-cmyk/mazarbul)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork mo-cmyk/mazarbul --clone && cd mazarbul
curl -s https://killerskills.ai/skills/glama/mazarbul/r1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/r1 && git commit -am "mazarbul: Collapsed <details> block carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/mazarbul/r1/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.