Propose a patch

Evidence

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

diff --git a/dist/adt/http.js b/dist/adt/http.js
--- a/dist/adt/http.js
+++ b/dist/adt/http.js
@@ -1193,1 +1193,0 @@
-const proxyToken = await awaitWithinRequestBudget(proxy.getProxyToken(), options);
@@ -1194,1 +1193,0 @@
-proxyAuth = `Bearer ${proxyToken}`;
diff --git a/dist/adt/config.d.ts b/dist/adt/config.d.ts
--- a/dist/adt/config.d.ts
+++ b/dist/adt/config.d.ts
@@ -68,1 +68,0 @@
-* When set, replaces the regular connectivity proxy token in the Proxy-Authorization header.

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.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: arc-1: Credential pass-through configuration (KillerSkills verdict caution 76)

## 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 76/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/arc-1/1.10.1

## Findings with a location
- `dist/adt/http.js:1194` · Credential pass-through configuration — dist/adt/http.js:1194 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/adt/http.js:1193` · Credential pass-through configuration — dist/adt/http.js:1193 · Credential pass-through configuration — agent relays sensitive credentials
- `dist/adt/config.d.ts:68` · Credential pass-through configuration — dist/adt/config.d.ts:68 · Credential pass-through configuration — agent relays sensitive credentials

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