← thetacog-mcp@2.61.0

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. 71 · 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
@@ -50,1 +50,0 @@
-Six seconds: the diff counter climbs to fourteen files in red — Steer it. — /steer typed, the agent line, then the Δ line placed and the Copy Run Summary door
@@ -835,1 +834,0 @@
-IN_LANE — sealed, placed at sense-axis A, byte-identical every run
@@ -1286,1 +1284,0 @@
-npx thetacog-mcp lens-run "<prompt>" --ideal <domain>   # run one prompt through the lens from the CLI — prints the readout, the retrieved rules, the template, and the domain match
diff --git a/scripts/rewrite/ui.html b/scripts/rewrite/ui.html
--- a/scripts/rewrite/ui.html
+++ b/scripts/rewrite/ui.html
@@ -151,1 +151,0 @@
-<summary>direction override — when rewriting cannot fix it</summary> <div class="row"> <input id="dir" class="mono" style="flex:1;background:#05070a;border:1px 

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.61.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: thetacog-mcp: Image alt text carrying instructions (KillerSkills verdict caution 71)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/thetacog-mcp/2.61.0

## Findings with a location
- `README.md:835` · Image alt text carrying instructions — README.md:835 · Image alt text carrying instructions
- `README.md:50` · Image alt text carrying instructions — README.md:50 · Image alt text carrying instructions
- `scripts/rewrite/ui.html:151` · Collapsed <details> block carrying instructions — scripts/rewrite/ui.html:151 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `README.md:1286` · Fake instruction boundary tag — README.md:1286 · Fake instruction boundary tag · informational: not an instruction file

## 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._
# or from a terminal, under your own account:
gh repo fork wiber/thetacog-mcp --clone && cd thetacog-mcp
curl -s https://killerskills.ai/skills/npm/thetacog-mcp/2.61.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/2.61.0 && git commit -am "thetacog-mcp: Image alt text carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/thetacog-mcp/2.61.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.