Propose a patch

Evidence

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

diff --git a/scripts/connect.mjs b/scripts/connect.mjs
--- a/scripts/connect.mjs
+++ b/scripts/connect.mjs
@@ -66,1 +66,0 @@
-output.write("Paste your API key (hidden), then press Enter: ");
diff --git a/test/connect.test.mjs b/test/connect.test.mjs
--- a/test/connect.test.mjs
+++ b/test/connect.test.mjs
@@ -112,1 +112,0 @@
-url.pathname.endsWith(".tgz") ? new Response(Buffer.from([0x1f, 0x8b, 3, 4])) : fetcher(url),

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.15. 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: ai-video-maker: Prompting user to enter sensitive credentials (KillerSkills verdict caution 72)

## 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 72/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/ai-video-maker/1.0.15

## Findings with a location
- `scripts/connect.mjs:66` · Prompting user to enter sensitive credentials — scripts/connect.mjs:66 · Prompting user to enter sensitive credentials — social engineering
- `test/connect.test.mjs:112` · Host or code assembled from base64 fragments — test/connect.test.mjs:112 · Host or code assembled from base64 fragments

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