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
@@ -91,1 +91,0 @@
-repo root. Do not hard-code or invent a recipe. If the user already has their own `~/.npmrc`
diff --git a/skills/sparkbtcbot/SKILL.md b/skills/sparkbtcbot/SKILL.md
--- a/skills/sparkbtcbot/SKILL.md
+++ b/skills/sparkbtcbot/SKILL.md
@@ -116,1 +116,0 @@
-…s/supply-chain.md` first: it says when to offer npm hardening (ask; persistent `~/.npmrc` vs ephemeral `NPM_CONFIG_*`), where the settings live (the `echennells/supply-…

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.10.1. 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: sparkbtcbot-skill: 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/npm/sparkbtcbot-skill/0.10.1

## Findings with a location
- `AGENTS.md:91` · References a credential file in the home directory — AGENTS.md:91 · References a credential file in the home directory
- `AGENTS.md:91` · Reads credential paths from the home directory — AGENTS.md:91 · Reads credential paths from the home directory
- `skills/sparkbtcbot/SKILL.md:116` · References a credential file in the home directory — skills/sparkbtcbot/SKILL.md:116 · 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._