Propose a patch

Evidence

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

diff --git a/AGENTS.md b/AGENTS.md
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -16,1 +16,0 @@
-- **SSH Config Support**: Automatically reads and uses settings from `~/.ssh/config`, including aliases, hosts, ports, users, and identity files
@@ -57,1 +56,0 @@
-The `host` parameter can be either a hostname/IP or an SSH config alias. If an SSH config alias is provided, configuration will be read from `~/.ssh/config`.
@@ -90,1 +88,0 @@
-key_filename="~/.ssh/id_rsa"
diff --git a/mcp_ssh_session/server.py b/mcp_ssh_session/server.py
--- a/mcp_ssh_session/server.py
+++ b/mcp_ssh_session/server.py
@@ -34,1 +34,0 @@
-If an SSH config alias is provided, configuration will be read from ~/.ssh/config.
@@ -119,1 +118,0 @@
-f"For example, if it's a password, provide the password followed by \\n."
diff --git a/Dockerfile b/Dockerfile
--- a/Dockerfile
+++ b/Dockerfile
@@ -112,1 +112,0 @@
--v ~/.ssh/id_rsa:/mounts/ssh-keys/id_rsa:ro \
@@ -113,1 +112,0 @@
--v ~/.ssh/id_rsa.pub:/mounts/ssh-keys/id_rsa.pub:ro \

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.2. 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: mcp-ssh-session: References a credential file in the home directory (KillerSkills verdict caution 68)

## 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 68/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/mcp-ssh-session/0.2.2

## Findings with a location
- `AGENTS.md:90` · References a credential file in the home directory — AGENTS.md:90 · References a credential file in the home directory
- `mcp_ssh_session/server.py:34` · Reads credential paths from the home directory — mcp_ssh_session/server.py:34 · Reads credential paths from the home directory
- `AGENTS.md:16` · Reads credential paths from the home directory — AGENTS.md:16 · Reads credential paths from the home directory
- `AGENTS.md:57` · Reads credential paths from the home directory — AGENTS.md:57 · Reads credential paths from the home directory
- `mcp_ssh_session/server.py:119` · Prompting user to enter sensitive credentials — mcp_ssh_session/server.py:119 · Prompting user to enter sensitive credentials — social engineering
- `Dockerfile:113` · References a credential file in the home directory — Dockerfile:113 · References a credential file in the home directory
- `Dockerfile:112` · References a credential file in the home directory — Dockerfile:112 · References a credential file in the home directory

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