Propose a patch

Evidence

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

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -173,1 +173,0 @@
-<summary><strong>Claude Code</strong></summary> Put this in `.mcp.json` in the project folder: ```json { "mcpServers": { "hindwatch": { "command": "npx", "args"
@@ -215,1 +214,0 @@
-<summary><strong>Codex</strong></summary> Run this in the project folder. This follows the Codex docs but has not yet been tried in a live Codex launch: ```sh c
@@ -265,1 +263,0 @@
-<summary><strong>Redaction</strong></summary> Redaction is always on and no config or plugin can turn it off. Every event is redacted before it reaches the buff
@@ -272,1 +269,0 @@
-<summary><strong>Project root and daemon lifecycle</strong></summary> The project root is the nearest folder with `hindwatch.config.json` or `package.json`. Pas

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

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

- See the findings below.

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

## Findings with a location
- `README.md:215` · Collapsed <details> block carrying instructions — README.md:215 · Collapsed <details> block carrying instructions
- `README.md:265` · Collapsed <details> block carrying instructions — README.md:265 · Collapsed <details> block carrying instructions
- `README.md:173` · Collapsed <details> block carrying instructions — README.md:173 · Collapsed <details> block carrying instructions
- `README.md:272` · Collapsed <details> block carrying instructions — README.md:272 · 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._