Propose a patch

Evidence

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

diff --git a/src/race_mcp/runtime/device_sources.py b/src/race_mcp/runtime/device_sources.py
--- a/src/race_mcp/runtime/device_sources.py
+++ b/src/race_mcp/runtime/device_sources.py
@@ -235,1 +235,0 @@
-# Usage: _identity_file_path_from_token("gpu", "gpu.example", "~/.ssh/id_ed25519")
@@ -254,1 +253,0 @@
-# Usage: _identity_file_readiness("gpu", "gpu.example", ["~/.ssh/id_ed25519"])
diff --git a/src/race_mcp/runtime/background_tmux.py b/src/race_mcp/runtime/background_tmux.py
--- a/src/race_mcp/runtime/background_tmux.py
+++ b/src/race_mcp/runtime/background_tmux.py
@@ -48,1 +48,0 @@
-"USER_CMD=$(base64 -d < \"$JOB_DIR/cmd.b64\")",
diff --git a/src/race_mcp/runtime/workspace.py b/src/race_mcp/runtime/workspace.py
--- a/src/race_mcp/runtime/workspace.py
+++ b/src/race_mcp/runtime/workspace.py
@@ -938,1 +938,0 @@
-"USER_CMD=$(printf '%s' \"$CMD_B64\" | base64 -d)",

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.3.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: race-mcp: 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/race-mcp/0.3.0

## Findings with a location
- `src/race_mcp/runtime/device_sources.py:254` · References a credential file in the home directory — src/race_mcp/runtime/device_sources.py:254 · References a credential file in the home directory
- `src/race_mcp/runtime/background_tmux.py:48` · Host or command assembled from base64 fragments — src/race_mcp/runtime/background_tmux.py:48 · Host or command assembled from base64 fragments
- `src/race_mcp/runtime/device_sources.py:254` · Reads credential paths from the home directory — src/race_mcp/runtime/device_sources.py:254 · Reads credential paths from the home directory
- `src/race_mcp/runtime/device_sources.py:235` · References a credential file in the home directory — src/race_mcp/runtime/device_sources.py:235 · References a credential file in the home directory
- `src/race_mcp/runtime/workspace.py:938` · Host or command assembled from base64 fragments — src/race_mcp/runtime/workspace.py:938 · Host or command assembled from base64 fragments

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