Propose a patch

Evidence

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

diff --git a/test/unit.test.ts b/test/unit.test.ts
--- a/test/unit.test.ts
+++ b/test/unit.test.ts
@@ -43,1 +43,0 @@
-["https://user:[email protected]/v2/?debug=1#top", "https://api.example.com/v2"],
diff --git a/test/tools.test.ts b/test/tools.test.ts
--- a/test/tools.test.ts
+++ b/test/tools.test.ts
@@ -404,1 +404,0 @@
-for (const input of [".env", path.join(home, ".ssh", "key.mp4"), "~/.ssh/id_rsa", "innocent.mp4", ".secrets/key.mp4"]) {
@@ -635,1 +634,0 @@
-video: file("video.mp4").replace("http://", "http://user:hunter2@"),

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: reelapi: URL with embedded credentials (KillerSkills verdict caution 74)

## 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 74/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/reelapi/0.1.0

## Findings with a location
- `test/unit.test.ts:43` · URL with embedded credentials — test/unit.test.ts:43 · URL with embedded credentials — may be phishing or credential leaking
- `test/tools.test.ts:635` · URL with embedded credentials — test/tools.test.ts:635 · URL with embedded credentials — may be phishing or credential leaking
- `test/tools.test.ts:404` · References a credential file in the home directory — test/tools.test.ts:404 · References a credential file in the home directory

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