← remoteshell-mcp@1.1.4

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. 62 · 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
@@ -39,1 +39,0 @@
-<summary><b>Antigravity</b></summary> Edit `~/.gemini/config/mcp_config.json` (global) or `.agents/mcp_config.json` (project): ```json { "mcpServers": { "remote
@@ -70,1 +69,0 @@
-<summary><b>Hermes Agent</b> (NousResearch)</summary> Edit `~/.hermes/config.yaml`: ```yaml mcp_servers: remoteshell: command: "uvx" args: ["remoteshell-mcp"] `
@@ -86,1 +84,0 @@
-<summary><b>OpenClaw</b></summary> Edit `~/.openclaw/openclaw.json`: ```json { "mcp": { "servers": { "remoteshell": { "command": "uvx", "args": ["remoteshell-mc
diff --git a/config.example.json b/config.example.json
--- a/config.example.json
+++ b/config.example.json
@@ -17,1 +17,0 @@
-"private_key": "~/.ssh/id_rsa",

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

## 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 62/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/remoteshell-mcp/1.1.4

## Findings with a location
- `README.md:39` · Collapsed <details> block carrying instructions — README.md:39 · Collapsed <details> block carrying instructions
- `README.md:86` · Collapsed <details> block carrying instructions — README.md:86 · Collapsed <details> block carrying instructions
- `README.md:70` · Collapsed <details> block carrying instructions — README.md:70 · Collapsed <details> block carrying instructions
- `config.example.json:17` · References a credential file in the home directory — config.example.json:17 · 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._
# or from a terminal, under your own account:
gh repo fork chouzz/remoteShell-mcp --clone && cd remoteShell-mcp
curl -s https://killerskills.ai/skills/pypi/remoteshell-mcp/1.1.4/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.1.4 && git commit -am "remoteshell-mcp: Collapsed <details> block carrying instructions"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/remoteshell-mcp/1.1.4/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.