← symbols-mcp@3.14.786

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 61 · Caution

Evidence

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

Diff · removes 2 caught lines

Download .patch
diff --git a/AGENTS.md b/AGENTS.md
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -1,1 +1,0 @@
-<!-- generated from CLAUDE.md (canonical) 2026-08-20 — edit CLAUDE.md, then re-copy -->
diff --git a/symbols_mcp/skills/DESIGN_SYSTEM.md b/symbols_mcp/skills/DESIGN_SYSTEM.md
--- a/symbols_mcp/skills/DESIGN_SYSTEM.md
+++ b/symbols_mcp/skills/DESIGN_SYSTEM.md
@@ -1242,1 +1242,0 @@
-url: 'https://fonts.googleapis.com/css2?family=Inter:[email protected]&display=swap',

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.14.786. 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: symbols-mcp: Instructs the agent to modify its persistent memory or instruction files (KillerSkills verdict caution 61)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 61/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/symbols-mcp/3.14.786

## Findings with a location
- `AGENTS.md:1` · Instructs the agent to modify its persistent memory or instruction files — AGENTS.md:1 · Instructs the agent to modify its persistent memory or instruction files
- `symbols_mcp/skills/DESIGN_SYSTEM.md:1242` · URL with embedded credentials — symbols_mcp/skills/DESIGN_SYSTEM.md:1242 · 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._
# or from a terminal, under your own account:
gh repo fork symbo-ls/symbols-mcp --clone && cd symbols-mcp
curl -s https://killerskills.ai/skills/pypi/symbols-mcp/3.14.786/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/3.14.786 && git commit -am "symbols-mcp: Instructs the agent to modify its persistent memory or instruction files"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/symbols-mcp/3.14.786/patch.md)

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.