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.
npx agentmods add skills/mailgun/mailgun-plugins/bounce-suppression-analysisnpx skills add mailgun/mailgun-plugins --skill bounce-suppression-analysisgit 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/skills/mailgun/mailgun-plugins/bounce-suppression-analysis)<a href="https://agentmods.dev/skills/mailgun/mailgun-plugins/bounce-suppression-analysis"><img src="https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/bounce-suppression-analysis.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00028 | $0.00374 |
| Opus 5 | $0.00014 | $0.00187 |
| Sonnet 5 | $0.00006 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
bounce-suppression-analysis 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 6d 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
Bounce and Suppression Analysis
Use this skill when the user asks about suppressed recipients, bounces, complaints, unsubscribes, or why Mailgun is dropping messages.
Intake
Collect the domain, date range, recipient or list segment if relevant, and whether the user wants analysis only or cleanup guidance.
Workflow
- Query suppression lists and recent logs for the domain.
- Separate bounces, complaints, unsubscribes, and allowlist entries.
- Identify whether drops are caused by suppressions, recent permanent failures, complaint policy, unsubscribes, or list hygiene problems.
- For individual recipients, check the narrowest relevant suppression type first.
- Recommend cleanup only after explaining the risk of sending to suppressed contacts again.
Interpretation
- Permanent failures, complaints, and unsubscribes can place recipients on suppression lists.
- Temporary failures usually retry and should not be treated the same as permanent bounces.
- A recipient on a suppression list can make later sends appear to vanish unless logs are checked.
- Repeated soft failures to the same recipient can still indicate a list quality problem.
- Complaint suppressions carry higher reputation risk than ordinary bounces and need extra caution before any allowlist action.
Safety
Never delete suppression entries, import suppressions, add allowlist entries, or resend to affected recipients without explicit confirmation. If the user asks to remove suppressions, restate the address, suppression type, domain, and expected consequence before proceeding.
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.
- 6d ago First seen · 38 lines · 28 tokens per session scan A a814d613dcc4
bounce-suppression-analysis is a skill published in the GitHub repository mailgun/mailgun-plugins (1 stars, last pushed 16d ago), licensed Apache-2.0. It adds 28 tokens to every session and 374 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…