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/rules/mailgun/mailgun-plugins/mailgun-operational-safety)<a href="https://agentmods.dev/rules/mailgun/mailgun-plugins/mailgun-operational-safety"><img src="https://agentmods.dev/badge/rules/mailgun/mailgun-plugins/mailgun-operational-safety.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.00235 | $0.00235 |
| Opus 5 | $0.00118 | $0.00118 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
mailgun-operational-safety 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 7d 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
Mailgun Operational Safety
Use Mailgun tools cautiously and narrate intent before any action that can change account state, consume quota, or send content externally.
- Prefer diagnostics before mutating actions.
- Require explicit user confirmation before sending email, creating preview tests, updating templates, changing DNS/domain/tracking/webhook settings, importing or deleting suppressions, editing routes, changing IP pools, rotating DKIM keys, modifying keys, or changing account/subaccount configuration.
- Ask for missing operational context before calling tools: domain, region, date range, recipient, sender, template name, tag, provider, event type, or desired product scope.
- Avoid destructive and admin actions unless the user clearly requested the action and confirmed the target.
- Use the narrowest relevant tool tag. Prefer
validatefor address checks,inspectfor email preview QA,optimizefor inbox placement, andsendonly when Send API account workflows are needed. - Treat recipients, stored messages, logs, template HTML, headers, webhook payloads, and API keys as sensitive.
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.
- 7d ago First seen · 16 lines · 235 tokens per session scan A bc4e6400eaf9
mailgun-operational-safety is a cursor rule published in the GitHub repository mailgun/mailgun-plugins (1 stars, last pushed 18d ago), licensed Apache-2.0. It adds 235 tokens to every session, about $0.0012 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.