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
@@ -41,1 +41,0 @@
-<summary><strong>Cursor</strong></summary> `~/.cursor/mcp.json` ```json { "mcpServers": { "relace": { "command": "uv", "args": ["tool", "run", "relace-mcp"], "e
@@ -63,1 +62,0 @@
-<summary><strong>Claude Code</strong></summary> ```bash claude mcp add relace \ --env RELACE_API_KEY=rlc-your-api-key \ --env MCP_BASE_DIR=/absolute/path/to/you
@@ -75,1 +73,0 @@
-<summary><strong>Windsurf</strong></summary> `~/.codeium/windsurf/mcp_config.json` ```json { "mcpServers": { "relace": { "command": "uv", "args": ["tool", "run"
@@ -97,1 +94,0 @@
-<summary><strong>VS Code</strong></summary> `.vscode/mcp.json` ```json { "mcp": { "servers": { "relace": { "type": "stdio", "command": "uv", "args": ["tool", "r
@@ -122,1 +118,0 @@
-<summary><strong>Codex CLI</strong></summary> `~/.codex/config.toml` ```toml [mcp_servers.relace] command = "uv" args = ["tool", "run", "relace-mcp"] [mcp_serve

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.4. 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: relace-mcp: Collapsed <details> block 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.8.1) 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/relace-mcp/0.2.4

## Findings with a location
- `README.md:63` · Collapsed <details> block carrying instructions — README.md:63 · Collapsed <details> block carrying instructions
- `README.md:97` · Collapsed <details> block carrying instructions — README.md:97 · Collapsed <details> block carrying instructions
- `README.md:75` · Collapsed <details> block carrying instructions — README.md:75 · Collapsed <details> block carrying instructions
- `README.md:41` · Collapsed <details> block carrying instructions — README.md:41 · Collapsed <details> block carrying instructions
- `README.md:122` · Collapsed <details> block carrying instructions — README.md:122 · Collapsed <details> block carrying instructions

## Proposed change
The attached patch removes the 5 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._