campaign-preflight

campaign-preflight is a skill for Claude Code from mailgun/mailgun-plugins. It costs 29 tokens per session (523 once invoked), scanned A, original, Apache-2.0.

A readiness review for a bulk or important Mailgun email send. It checks the sender, recipients, suppressions, message content, previews, and operational details before sending.

In plain words
What is it for?
It helps prepare campaigns, launches, migration notices, and other sizable sends by reviewing DNS, sender identity, audience quality, content, timing, and expected volume.
Why use it?
It helps catch unverified domains, risky recipients, missing unsubscribe links, broken template variables, and other problems that can harm delivery or send safety.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the mailgun-claude plugin — 15 skills, 7 commands, 1 MCP server shipped together

Good fit It helps prepare campaigns, launches, migration notices, and other sizable sends by reviewing DNS, sender identity, audience quality, content, timing, and expected volume.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mailgun/mailgun-plugins/campaign-preflight
Install

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.

Any agent
npx skills add mailgun/mailgun-plugins --skill campaign-preflight
Clone the repo
git clone --depth 1 https://github.com/mailgun/mailgun-plugins

Made for: Claude Code.

Or install mailgun-claude, the plugin that ships this one along with the rest of its 15 skills, 7 commands, 1 MCP server.

Wrote 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.

agentmods badge for campaign-preflight

README.md
[![agentmods](https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/campaign-preflight/github.svg)](https://agentmods.dev/skills/mailgun/mailgun-plugins/campaign-preflight)
Your own site
<a href="https://agentmods.dev/skills/mailgun/mailgun-plugins/campaign-preflight"><img src="https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/campaign-preflight/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.

agentmods 80×15 button for campaign-preflight

Your own site · 80×15
<a href="https://agentmods.dev/skills/mailgun/mailgun-plugins/campaign-preflight"><img src="https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/campaign-preflight.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 523 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00523
Opus 5.5 $0.00012 $0.00209
Sonnet 5.5 $0.00006 $0.00105
Haiku 4.5 $0.00003 $0.00052

Measured 2mo ago against content hash 0f09d139e1a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

campaign-preflight 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 2mo 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.

plugins/mailgun-claude/skills/campaign-preflight/SKILL.md · 42 lines

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.

Campaign Preflight

Use this skill when the user is preparing a bulk send, campaign, launch announcement, migration notice, or any message where delivery quality and safety matter before sending.

Use sending and template QA for a simple test message. Use this skill when the workflow needs readiness checks across sender identity, audience, content, and operational risk.

Intake

Ask for domain, region, sender identity, recipient source or list segment, message purpose, template or content, expected volume, send timing, and whether the user wants planning only or a live send.

Workflow

  1. Confirm the domain exists in the expected region and DNS verification is healthy.
  2. Check sender identity readiness: recognizable From address, verified domain, tracking settings, and whether the domain or IP is cold.
  3. Review recipients before sending. Use Validate when checking individual addresses or samples, and review suppressions, unsubscribes, complaints, and allowlist entries when relevant.
  4. Review the template or content. Confirm variables, text and HTML coverage, unsubscribe or preference links for bulk mail, and brand alignment.
  5. Prefer Inspect preview QA for HTML rendering, links, images, accessibility, and code analysis before production use.
  6. Check recent logs, metrics, bounce classification, and existing inbox placement results when the user has enough account data and the campaign has reputation risk.
  7. Produce a go, hold, or fix first recommendation with evidence and specific next steps.

Bulk Send Guardrails

  • Treat bulk sends as higher risk than transactional tests.
  • Avoid sending to purchased, scraped, stale, or unvalidated lists.
  • Recommend gradual rollout for cold domains, cold IPs, new sender identities, or unusually large volume jumps.
  • Confirm exclusions for unsubscribes, complaints, bounces, and internal suppression rules before recommending a live send.
  • If batch personalization is used, validate recipient-variables JSON and check that required variables exist.

Read the full file on GitHub · 42 lines

Changes

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.

  1. 2mo ago First seen · 42 lines · 29 tokens per session scan A 0f09d139e1a4

Subscribe to this mod's changes

campaign-preflight is a skill published in the GitHub repository mailgun/mailgun-plugins (2 stars, last pushed 15d ago), licensed Apache-2.0. It adds 29 tokens to every session and 523 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens