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. 79 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 10 caught lines
Download .patchdiff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -214,1 +214,0 @@
-**2. Make it automatic — add a rule to your `CLAUDE.md`** (a project one, or global `~/.claude/CLAUDE.md`)
@@ -233,1 +232,0 @@
-skim-mcp install --rule global # write the rule to ~/.claude/CLAUDE.md instead
@@ -256,1 +254,0 @@
-skim live token-savings dashboard: 76.5% saved overall, 261,826 tokens in, 61,452 out, a By-session table (docs-pass 79.4%, api-refactor 74.7%) with last-active
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -9,1 +9,0 @@
-What did you run, what did you expect, what did you get instead?
diff --git a/src/skim/install.py b/src/skim/install.py
--- a/src/skim/install.py
+++ b/src/skim/install.py
@@ -9,1 +9,0 @@
-skim-mcp install --rule global # write the rule to ~/.claude/CLAUDE.md instead
@@ -101,1 +100,0 @@
-description="Register skim with Claude Code and write the CLAUDE.md preference rule "
@@ -105,1 +103,0 @@
-help="where to write the prefer-skim rule (default: ./CLAUDE.md)")
diff --git a/tests/test_regressions.py b/tests/test_regressions.py
--- a/tests/test_regressions.py
+++ b/tests/test_regressions.py
@@ -19,1 +19,0 @@
-("import os\n", ".py"), # leading BOM
diff --git a/PKG-INFO b/PKG-INFO
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -249,1 +249,0 @@
-**2. Make it automatic — add a rule to your `CLAUDE.md`** (a project one, or global `~/.claude/CLAUDE.md`)
@@ -268,1 +267,0 @@
-skim-mcp install --rule global # write the rule to ~/.claude/CLAUDE.md instead
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.1. 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: skim-mcp: Image alt text carrying instructions (KillerSkills verdict caution 79)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 79/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/skim-mcp/0.1.1 ## Findings with a location - `README.md:256` · Image alt text carrying instructions — README.md:256 · Image alt text carrying instructions - `.github/ISSUE_TEMPLATE/bug_report.md:9` · HTML comment carrying imperative instructions to the agent — .github/ISSUE_TEMPLATE/bug_report.md:9 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file - `src/skim/install.py:105` · Instructs the agent to modify its persistent memory or instruction files — src/skim/install.py:105 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `tests/test_regressions.py:19` · Hidden zero-width characters detected — tests/test_regressions.py:19 · Hidden zero-width characters detected — may conceal content - `src/skim/install.py:101` · Instructs the agent to modify its persistent memory or instruction files — src/skim/install.py:101 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `README.md:233` · Instructs the agent to modify its persistent memory or instruction files — README.md:233 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `PKG-INFO:268` · Instructs the agent to modify its persistent memory or instruction files — PKG-INFO:268 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `README.md:214` · Instructs the agent to modify its persistent memory or instruction files — README.md:214 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `PKG-INFO:249` · Instructs the agent to modify its persistent memory or instruction files — PKG-INFO:249 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `src/skim/install.py:9` · Instructs the agent to modify its persistent memory or instruction files — src/skim/install.py:9 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file ## Proposed change The attached patch removes the 10 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 helloderekg/skim-mcp --clone && cd skim-mcp curl -s https://killerskills.ai/skills/pypi/skim-mcp/0.1.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.1.1 && git commit -am "skim-mcp: Image alt text carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/skim-mcp/0.1.1/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.