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 4 caught lines

Download .patch

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -84,1 +84,0 @@
-<summary><strong>Other install methods</strong></summary> **Claude Code plugin only** (no system package): ```bash claude plugin marketplace add Q00/ouroboros &
@@ -131,1 +130,0 @@
-<summary><strong>What just happened?</strong></summary> ``` interview -> Socratic questioning exposed 12 hidden assumptions seed -> Crystallized answers into an
diff --git a/skills/setup/SKILL.md b/skills/setup/SKILL.md
--- a/skills/setup/SKILL.md
+++ b/skills/setup/SKILL.md
@@ -231,1 +231,0 @@
-Add Ouroboros quick-reference to your CLAUDE.md?
diff --git a/skills/update/SKILL.md b/skills/update/SKILL.md
--- a/skills/update/SKILL.md
+++ b/skills/update/SKILL.md
@@ -150,1 +150,0 @@
-d. **Verify and update CLAUDE.md version marker**:

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: ouroboros: Collapsed <details> block carrying instructions (KillerSkills verdict caution 62)

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

- See the findings below.

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

## Findings with a location
- `README.md:84` · Collapsed <details> block carrying instructions — README.md:84 · Collapsed <details> block carrying instructions
- `README.md:131` · Collapsed <details> block carrying instructions — README.md:131 · Collapsed <details> block carrying instructions
- `skills/setup/SKILL.md:231` · Instructs the agent to modify its persistent memory or instruction files — skills/setup/SKILL.md:231 · Instructs the agent to modify its persistent memory or instruction files
- `skills/update/SKILL.md:150` · Instructs the agent to modify its persistent memory or instruction files — skills/update/SKILL.md:150 · Instructs the agent to modify its persistent memory or instruction files

## Proposed change
The attached patch removes the 4 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 (ACRT-EVAL/ouroboros-234-cr5)Fork to open a PR

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