Propose a patch

Evidence

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

diff --git a/scripts/demo.sh b/scripts/demo.sh
--- a/scripts/demo.sh
+++ b/scripts/demo.sh
@@ -75,1 +75,0 @@
-echo "-----fake key material-----" > "$HOME/.ssh/id_demo"
@@ -119,1 +118,0 @@
-cat "$HOME/Documents/taxes.txt" "$HOME/.ssh/id_demo" "$DEMO/victim/keep.txt"

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.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: disk-janitor-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/glama/disk-janitor-mcp/0.1.0

## Findings with a location
- `scripts/demo.sh:119` · References a credential file in the home directory — scripts/demo.sh:119 · References a credential file in the home directory
- `scripts/demo.sh:119` · Reads credential paths from the home directory — scripts/demo.sh:119 · Reads credential paths from the home directory
- `scripts/demo.sh:75` · References a credential file in the home directory — scripts/demo.sh:75 · References a credential file in the home directory

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