Propose a patch

Evidence

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

diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -40,1 +40,0 @@
-…xt the user pastes in to be saved. Store the pointer and strip the value: `file:~/.ssh/id_ed25519`, `keychain:hetzner-api`, `1password:Infra/root-password`, `env:RESTIC_P…
@@ -217,1 +216,0 @@
-… any of them into `~/Clawic/data/`. Only pointers are stored, in the form `file:~/.ssh/id_ed25519` or `keychain:<entry>`. **Local storage:** host inventory, provider acc…
diff --git a/security.md b/security.md
--- a/security.md
+++ b/security.md
@@ -127,1 +127,0 @@
-…estore timed within the quarter | An untested backup is not a control | --- **Write it down.** An exposure sweep updates `## Exposure` in `~/Clawic/data/vps/memory.md`; anything it turned up that is not already inventoried goes to `~/Clawic/data/…
diff --git a/firewall.md b/firewall.md
--- a/firewall.md
+++ b/firewall.md
@@ -104,1 +104,0 @@
-…ing unexpected goes into `## Exposure` with its reason, or gets closed. --- **Write it down.** Every open port belongs in `## Exposure` in `~/Clawic/data/vps/memory.md`: host, port, service, what it is open to, why, and the layer the rule lives at…
diff --git a/choosing.md b/choosing.md
--- a/choosing.md
+++ b/choosing.md
@@ -82,1 +82,0 @@
-…nd its real cost, the accepted downsides, and what would make you revisit — and add its `## Boxes` line to `memory.md` in the same turn. Deriving this comparison takes an afternoon; nobody should p…
diff --git a/access.md b/access.md
--- a/access.md
+++ b/access.md
@@ -117,1 +117,0 @@
-…lable, the console path by name, the cause, and what would have made it faster. Add its `## Boxes` line to `memory.md` in the same turn with the read condition "SSH to `<host>` refuses or times out…

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

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/vps/1.0.2

## Findings with a location
- `SKILL.md:217` · References a credential file in the home directory — SKILL.md:217 · References a credential file in the home directory
- `security.md:127` · Instructs the agent to modify its persistent memory or instruction files — security.md:127 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `firewall.md:104` · Instructs the agent to modify its persistent memory or instruction files — firewall.md:104 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `choosing.md:82` · Instructs the agent to modify its persistent memory or instruction files — choosing.md:82 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `SKILL.md:40` · References a credential file in the home directory — SKILL.md:40 · References a credential file in the home directory
- `access.md:117` · Instructs the agent to modify its persistent memory or instruction files — access.md:117 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

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