← mcp-agent-mail@0.1.0

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. 65 · Caution

Evidence

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

Diff · removes 3 caught lines

Download .patch
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -98,1 +98,0 @@
-# Now, simply launch Codex-CLI or Claude Code or other agent tools in other consoles; they should have the mail tool available. See below for a ready-made chunk of text you can add to the end of your 
@@ -104,1 +103,0 @@
-## Ready-Made Blurb to Add to Your AGENTS.md or CLAUDE.md Files:
diff --git a/src/mcp_agent_mail/templates/mail_thread.html b/src/mcp_agent_mail/templates/mail_thread.html
--- a/src/mcp_agent_mail/templates/mail_thread.html
+++ b/src/mcp_agent_mail/templates/mail_thread.html
@@ -62,1 +62,0 @@
-Message Header (Always Visible)

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

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/mcp-agent-mail/0.1.0

## Findings with a location
- `README.md:98` · Instructs the agent to modify its persistent memory or instruction files — README.md:98 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `README.md:104` · Instructs the agent to modify its persistent memory or instruction files — README.md:104 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `src/mcp_agent_mail/templates/mail_thread.html:62` · HTML comment carrying imperative instructions to the agent — src/mcp_agent_mail/templates/mail_thread.html:62 · HTML comment carrying imperative instructions to the agent · 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._
# or from a terminal, under your own account:
gh repo fork jleechanorg/mcp_agent_mail --clone && cd mcp_agent_mail
curl -s https://killerskills.ai/skills/pypi/mcp-agent-mail/0.1.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.1.0 && git commit -am "mcp-agent-mail: Instructs the agent to modify its persistent memory or instruction files"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/mcp-agent-mail/0.1.0/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.