Propose a patch

Evidence

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

diff --git a/public/index.html b/public/index.html
--- a/public/index.html
+++ b/public/index.html
@@ -54,1 +54,0 @@
-<summary>📥 Import from GitHub instead — one click per repo</summary> <div class="row"><input id="ghOwner" placeholder="GitHub username (e.g. CloudCorpRecords)"
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -7,1 +7,0 @@
-Required, and never held against you: human / ai-assisted / ai-built / agent. If AI helped, which parts?

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

## 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 75/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/opensourceit/0.5.1

## Findings with a location
- `package.json:1` · URL with embedded credentials — package.json:1 · URL with embedded credentials — may be phishing or credential leaking
- `public/index.html:54` · Collapsed <details> block carrying instructions — public/index.html:54 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `.github/PULL_REQUEST_TEMPLATE.md:7` · HTML comment carrying imperative instructions to the agent — .github/PULL_REQUEST_TEMPLATE.md:7 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file

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