Propose a patch

Evidence

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

diff --git a/site/index.html b/site/index.html
--- a/site/index.html
+++ b/site/index.html
@@ -81,1 +81,0 @@
-<summary>Running several clients at once?</summary><p>Use one shared HTTP process for the bot and database. Configure your private <code>.env</code> from the <a
diff --git a/test/connector.test.ts b/test/connector.test.ts
--- a/test/connector.test.ts
+++ b/test/connector.test.ts
@@ -148,1 +148,0 @@
-…Address('8.8.8.8'), true); for (const url of ['http://receiver.example.com', 'https://user:[email protected]', 'https://receiver.example.com:444/', 'https://evil.exampl…

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.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: tg2codexmcp: Collapsed <details> block carrying instructions (KillerSkills verdict caution 78)

## 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 78/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/tg2codexmcp/0.2.0

## Findings with a location
- `site/index.html:81` · Collapsed <details> block carrying instructions — site/index.html:81 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `test/connector.test.ts:148` · URL with embedded credentials — test/connector.test.ts:148 · URL with embedded credentials — may be phishing or credential leaking

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