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/platform-operatornpx skills add mailgun/mailgun-plugins --skill platform-operatorgit 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/platform-operator)<a href="https://agentmods.dev/skills/mailgun/mailgun-plugins/platform-operator"><img src="https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/platform-operator.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 | $0.00036 | $0.00523 |
| Opus 5 | $0.00018 | $0.00262 |
| Sonnet 5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
platform-operator 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Operator
Use this skill when the user runs a SaaS, martech, developer platform, or other service that lets its own customers send email through Mailgun.
Do not use this skill for a single sender managing only its own email program. Use deliverability triage, domain onboarding, or sending QA instead.
Intake
Ask for the tenant model, subaccount structure, domain ownership model, send volume, IP pool setup, abuse handling process, and whether the user wants architecture guidance or account diagnostics.
Workflow
- Identify whether each tenant has its own subaccount, domain, API key scope, and suppression boundary.
- Review sender onboarding gates: business identity, domain verification, domain age, impersonation risk, and first send limits.
- Check progressive trust controls: daily caps for new senders, advancement criteria, and rollback paths for risky senders.
- Review monitoring signals across tenants: hard bounces, complaints, spam trap indicators, blocklist signals, provider throttling, volume spikes, and suppression growth.
- Inspect IP and pool strategy when available: shared pools, dedicated pools, quarantine pools, warmup status, and tenant isolation.
- Summarize operational gaps and recommend next steps, separating advisory changes from actions that modify the Mailgun account.
Operating Guidance
- A platform is accountable for the mail sent through its Mailgun account, even when tenants provide the content and recipient lists.
- Require domain verification before meaningful production sending.
- Treat complaint rates near or above 0.1 percent as urgent, especially for new tenants.
- Pause or limit tenants with sharp bounce spikes, complaint spikes, spam trap indicators, or sudden volume changes until reviewed.
- Maintain a monitored abuse mailbox, complaint intake process, human review queue, and tenant notification path.
- Avoid mixing all tenants into one undifferentiated reputation pool when volume and risk justify stronger isolation.
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.
- 3d ago First seen · 42 lines · 36 tokens per session scan A 77526c2a765b
platform-operator is a skill published in the GitHub repository mailgun/mailgun-plugins (1 stars, last pushed 14d ago), licensed Apache-2.0. It adds 36 tokens to every session and 523 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…