Propose a patch

Evidence

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

diff --git a/dist/chunk-TL2HK6LZ.js b/dist/chunk-TL2HK6LZ.js
--- a/dist/chunk-TL2HK6LZ.js
+++ b/dist/chunk-TL2HK6LZ.js
@@ -146,1 +146,0 @@
-return `https://x-access-token:${encodeURIComponent(token)}@github.com
diff --git a/dist/chunk-R4W4VQJZ.js b/dist/chunk-R4W4VQJZ.js
--- a/dist/chunk-R4W4VQJZ.js
+++ b/dist/chunk-R4W4VQJZ.js
@@ -144,1 +144,0 @@
-return `https://x-access-token:${encodeURIComponent(token)}@github.com
diff --git a/dist/index.d.ts b/dist/index.d.ts
--- a/dist/index.d.ts
+++ b/dist/index.d.ts
@@ -6818,1 +6818,0 @@
-* Write the fleet playbook to AGENTS.md in the global synthetic cwd. CLAUDE.md

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.338. 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: core: URL with embedded credentials (KillerSkills verdict caution 68)

## 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 68/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/core/0.1.338

## Findings with a location
- `dist/chunk-TL2HK6LZ.js:146` · URL with embedded credentials — dist/chunk-TL2HK6LZ.js:146 · URL with embedded credentials — may be phishing or credential leaking
- `dist/chunk-R4W4VQJZ.js:144` · URL with embedded credentials — dist/chunk-R4W4VQJZ.js:144 · URL with embedded credentials — may be phishing or credential leaking
- `dist/index.d.ts:6818` · Instructs the agent to modify its persistent memory or instruction files — dist/index.d.ts:6818 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

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