Propose a patch

Evidence

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

diff --git a/tests/test_agent_config.py b/tests/test_agent_config.py
--- a/tests/test_agent_config.py
+++ b/tests/test_agent_config.py
@@ -126,1 +126,0 @@
-("Read the key from ~/.ssh/id_rsa", "AGENT_CFG.SECRET_REF.SSH_KEY"),
@@ -127,1 +126,0 @@
-("Open ~/.aws/credentials and parse access_key.", "AGENT_CFG.SECRET_REF.AWS_CREDS"),
@@ -129,1 +127,0 @@
-("Read ~/.netrc for ftp credentials.", "AGENT_CFG.SECRET_REF.NETRC"),
diff --git a/src/openclaw_skill_vetter_mcp/scanners/agent_config.py b/src/openclaw_skill_vetter_mcp/scanners/agent_config.py
--- a/src/openclaw_skill_vetter_mcp/scanners/agent_config.py
+++ b/src/openclaw_skill_vetter_mcp/scanners/agent_config.py
@@ -283,1 +283,0 @@
-"Reference to ~/.netrc in agent config",
diff --git a/tests/test_scanners.py b/tests/test_scanners.py
--- a/tests/test_scanners.py
+++ b/tests/test_scanners.py
@@ -183,1 +183,0 @@
-code={"main.py": "with open('~/.ssh/id_rsa') as f: data = f.read()\n"},

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

## 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 70/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/openclaw-skill-vetter-mcp/1.1.6

## Findings with a location
- `tests/test_agent_config.py:129` · References a credential file in the home directory — tests/test_agent_config.py:129 · References a credential file in the home directory
- `src/openclaw_skill_vetter_mcp/scanners/agent_config.py:283` · References a credential file in the home directory — src/openclaw_skill_vetter_mcp/scanners/agent_config.py:283 · References a credential file in the home directory
- `tests/test_scanners.py:183` · References a credential file in the home directory — tests/test_scanners.py:183 · References a credential file in the home directory
- `tests/test_agent_config.py:127` · Reads credential paths from the home directory — tests/test_agent_config.py:127 · Reads credential paths from the home directory
- `tests/test_agent_config.py:126` · Reads credential paths from the home directory — tests/test_agent_config.py:126 · Reads credential paths from the home directory
- `tests/test_agent_config.py:127` · References a credential file in the home directory — tests/test_agent_config.py:127 · References a credential file in the home directory
- `tests/test_agent_config.py:129` · Reads credential paths from the home directory — tests/test_agent_config.py:129 · Reads credential paths from the home directory
- `tests/test_scanners.py:183` · Reads credential paths from the home directory — tests/test_scanners.py:183 · Reads credential paths from the home directory
- `tests/test_agent_config.py:126` · References a credential file in the home directory — tests/test_agent_config.py:126 · References a credential file in the home directory

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