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 commands/fergupa/claude_plugins/campaign-plangit clone --depth 1 https://github.com/fergupa/claude_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/commands/fergupa/claude_plugins/campaign-plan)<a href="https://agentmods.dev/commands/fergupa/claude_plugins/campaign-plan"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/campaign-plan.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.00016 | $0.00932 |
| Opus 5 | $0.00008 | $0.00466 |
| Sonnet 5 | $0.00003 | $0.00186 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
campaign-plan 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 yesterday.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Campaign Plan
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a comprehensive marketing campaign brief with objectives, audience, messaging, channel strategy, content calendar, and success metrics.
Trigger
User runs /campaign-plan or asks to plan, design, or build a marketing campaign.
Inputs
Gather the following from the user. If not provided, ask before proceeding:
-
Campaign goal — the primary objective (e.g., drive signups, increase awareness, launch a product, generate leads, re-engage churned users)
-
Target audience — who the campaign is aimed at (demographics, roles, industries, pain points, buying stage)
-
Timeline — campaign duration and any fixed dates (launch date, event date, seasonal deadline)
-
Budget range — approximate budget or budget tier (optional; if not provided, generate a channel-agnostic plan and note where budget allocation would matter)
-
Additional context (optional):
- Product or service being promoted
- Key differentiators or value propositions
- Previous campaign performance or learnings
- Brand guidelines or constraints
- Geographic focus
Campaign Brief Structure
Generate a campaign brief with the following sections:
1. Campaign Overview
- Campaign name suggestion
- One-sentence campaign summary
- Primary objective with a specific, measurable goal
- Secondary objectives (if applicable)
2. Target Audience
- Primary audience segment with description
- Secondary audience segment (if applicable)
- Audience pain points and motivations
- Where they spend time (channels, communities, publications)
- Buying stage alignment (awareness, consideration, decision)
3. Key Messages
- Core campaign message (one sentence)
- 3-4 supporting messages tailored to audience pain points
- Message variations by channel (if different tones are needed)
- Proof points or evidence to support each message
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.
- yesterday First seen · 121 lines · 16 tokens per session scan A 8daa883be0c1
campaign-plan is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 932 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.