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
@@ -161,1 +161,0 @@
-<summary><b><code>PRIME_API_KEY is not set</code></b></summary> Either your Claude Code config didn't pick up the `env` block, or you typed `PRIME_API_KEY` as a
@@ -179,1 +178,0 @@
-<summary><b><code>Quote token expired</code></b></summary> Quotes live 60 seconds; the agent waited too long between `pod_quote` and `pod_create`. Just call `po
@@ -191,1 +189,0 @@
-<summary><b><code>ssh: Permission denied (publickey)</code></b></summary> You haven't told Prime Intellect about your public key (or the pod was provisioned bef
diff --git a/src/prime_intellect_mcp/server.py b/src/prime_intellect_mcp/server.py
--- a/src/prime_intellect_mcp/server.py
+++ b/src/prime_intellect_mcp/server.py
@@ -454,1 +454,0 @@
-"Ensure you've run `prime config set-ssh-key-path ~/.ssh/id_ed25519` "

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.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: prime-intellect-mcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 55)

## 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 55/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/prime-intellect-mcp/0.1.0

## Findings with a location
- `README.md:191` · Collapsed <details> block carrying instructions — README.md:191 · Collapsed <details> block carrying instructions
- `README.md:161` · Collapsed <details> block carrying instructions — README.md:161 · Collapsed <details> block carrying instructions
- `README.md:179` · Collapsed <details> block carrying instructions — README.md:179 · Collapsed <details> block carrying instructions
- `src/prime_intellect_mcp/server.py:454` · References a credential file in the home directory — src/prime_intellect_mcp/server.py:454 · References a credential file in the home directory

## 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._