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. 57 · 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
@@ -125,1 +125,0 @@
-<summary><b>Installer options</b></summary> <br> | Variable | Default | Meaning | |---|---|---| | `UNABRIDGED_REF` | latest release | tag, branch or commit to i
@@ -235,1 +234,0 @@
-<summary><b>Add the MCP server by hand</b></summary> <br> Claude Code (without the plugin): ```bash claude mcp add unabridged -- npx -y https://github.com/saiee
diff --git a/skills/export-transcripts/SKILL.md b/skills/export-transcripts/SKILL.md
--- a/skills/export-transcripts/SKILL.md
+++ b/skills/export-transcripts/SKILL.md
@@ -12,1 +12,0 @@
-unabridged:run
@@ -18,1 +17,0 @@
-/unabridged:run

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

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 57/100**. Summary: calls github.com only, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/cc-exporter/0.2.0

## Findings with a location
- `README.md:235` · Collapsed <details> block carrying instructions — README.md:235 · Collapsed <details> block carrying instructions
- `skills/export-transcripts/SKILL.md:12` · HTML comment carrying imperative instructions to the agent — skills/export-transcripts/SKILL.md:12 · HTML comment carrying imperative instructions to the agent
- `skills/export-transcripts/SKILL.md:18` · HTML comment carrying imperative instructions to the agent — skills/export-transcripts/SKILL.md:18 · HTML comment carrying imperative instructions to the agent
- `README.md:125` · Collapsed <details> block carrying instructions — README.md:125 · Collapsed <details> block carrying instructions

## 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 (saieeshb/unabridged)Fork to open a PR

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