Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/didvc/claude-email-leak-noticeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/didvc/claude-email-leak-notice/email-leak-notice)<a href="https://agentmods.dev/plugins/didvc/claude-email-leak-notice/email-leak-notice"><img src="https://agentmods.dev/badge/plugins/didvc/claude-email-leak-notice/email-leak-notice/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/didvc/claude-email-leak-notice/email-leak-notice"><img src="https://agentmods.dev/badge/plugins/didvc/claude-email-leak-notice/email-leak-notice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
email-leak-notice scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"name": "email-leak-notice",
"displayName": "Email Leak Notice",
"version": "0.1.0",
"description": "Claude Code injects your account email into session context, where an agent may reuse it as a legitimate value and commit it. This warns once per session when a personal address appears in a tool payload. Never blocks.",
"author": {
"name": "didvc",
"url": "https://github.com/didvc"
},
"repository": "https://github.com/didvc/claude-email-leak-notice",
"license": "MIT",
"keywords": ["privacy", "email", "pii", "git", "hooks", "safety"]
}
What it installs
The manifest is a name and a version. 1 hook travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 14 lines scan A 5d8d29792616
email-leak-notice is a plugin published in the GitHub repository didvc/claude-email-leak-notice (1 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
branch-guard
Cut routine git/gh approval prompts: auto-approve safe commands (read-only, staging, branch/worktree create, feature-branch commits & pushes) and confirm protected-branch or destructive ones.
exit-status-guard
Deny shell commands whose exit status is the answer and gets lost.
foreground-guard
Main-thread time guard for Claude Code Bash commands: catch foreground polling/watching and slow commands about to be killed by an inadequate timeout.
workspace-guard
Workspace-boundary shell permissions for Claude Code.
claude-timestamp
Stamps every message with the local time and how long the turn took, names the tool behind a slow turn, and reports where a session's time actually went. Claude receives the send time of each prompt, so it can reason about when things happened.
usage-guard
Injects fresh 5h/weekly quota into Claude's context on every prompt, warns before plan limits, and celebrates resets. Zero dependencies; network off unless optional ntfy is configured.