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/mailgun/mailgun-pluginsWrote 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/mailgun/mailgun-plugins/mailgun-claude)<a href="https://agentmods.dev/plugins/mailgun/mailgun-plugins/mailgun-claude"><img src="https://agentmods.dev/badge/plugins/mailgun/mailgun-plugins/mailgun-claude/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/mailgun/mailgun-plugins/mailgun-claude"><img src="https://agentmods.dev/badge/plugins/mailgun/mailgun-plugins/mailgun-claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mailgun-claude 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 1mo 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": "mailgun-claude",
"author": {
"name": "Mailgun",
"email": "[email protected]",
"url": "https://github.com/mailgun"
},
"version": "0.1.1",
"description": "Claude Code plugin for Mailgun email, deliverability, suppression, template, Inspect, Optimize, Validate, and reporting workflows.",
"homepage": "https://www.mailgun.com/",
"repository": "https://github.com/mailgun/mailgun-plugins",
"license": "Apache-2.0",
"keywords": ["mailgun", "email", "deliverability", "dns", "suppression", "templates", "mcp"],
"commands": [
"./commands/mailgun-setup.md",
"./commands/audit-domain-health.md",
"./commands/investigate-bounces-last-7-days.md",
"./commands/verify-dns-for-domain.md",
"./commands/review-suppressions-for-domain.md",
"./commands/draft-test-email-template.md",
"./commands/compare-delivery-across-domains.md"
],
"skills": "./skills",
"mcpServers": "./.mcp.json"
}
What it installs
The manifest is a name and a version. 15 skills, 7 commands, 1 MCP server travel with it, and installing the plugin installs all of them — 568 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill address-validation A 26 tokens
- Skill campaign-preflight A 29 tokens
- Skill platform-operator A 36 tokens
- Skill sending-template-qa A 22 tokens
- Skill bounce-rate-explanation A 31 tokens
- Skill deliverability-triage A 29 tokens
- Skill domain-onboarding-dns-verification A 30 tokens
- Skill inbound-routing-troubleshooting A 32 tokens
- Skill missing-email-investigation A 33 tokens
- Skill post-send-analysis A 31 tokens
- Skill sending-health-check A 36 tokens
- Skill bounce-suppression-analysis A 28 tokens
- Skill cross-domain-reporting A 22 tokens
- Skill engagement-analysis A 24 tokens
- Skill mcp-troubleshooting A 30 tokens
- Command mailgun-setup A 14 tokens
- Command audit-domain-health A 19 tokens
- Command compare-delivery-across-domains A 17 tokens
- Command draft-test-email-template A 16 tokens
- Command investigate-bounces-last-7-days A 24 tokens
- Command review-suppressions-for-domain A 25 tokens
- Command verify-dns-for-domain A 14 tokens
- MCP server mailgun A not measured
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.
- 1mo ago Changed 42cd2dcaec8c
- 2mo ago First seen · 26 lines scan A 502f02e4960a
mailgun-claude is a plugin published in the GitHub repository mailgun/mailgun-plugins (2 stars, last pushed 15d ago), licensed Apache-2.0. 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
app-builder
Development, customization, testing, and deployment skills for Adobe App Builder projects, including the Workfront UI-extension suite (skills/appbuilder-workfront).
rails-consultant
A collection of skills for Rails development and consulting, with an emphasis on learning, communication, and client success.
load-tester
Load and stress testing for APIs and web services.
rabbitmqadmin
Skill for inspecting RabbitMQ instances using the rabbitmqadmin CLI (rabbitmqadmin-ng).
jpm-payments-skills
Conversational agent skills that walk a merchant from J.P. Morgan Payments onboarding through a working API integration. Supports Checkout and Online Payments in the initial release. Generates language-specific OAuth modules (Node/TypeScript, Python, Java idiomatic; other languages via canonical algorithm).
auth
Auth skills for Claude Code — scaffold hand-rolled auth endpoints and audit auth code against security best practices.