Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pronpx agentmods add commands/indranilbanerjee/digital-marketing-pro/campaign-planWrote 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/indranilbanerjee/digital-marketing-pro/campaign-plan)<a href="https://agentmods.dev/commands/indranilbanerjee/digital-marketing-pro/campaign-plan"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/campaign-plan/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.
<a href="https://agentmods.dev/commands/indranilbanerjee/digital-marketing-pro/campaign-plan"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/campaign-plan.svg" alt="Reviewed on agentmods" width="80" 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.00022 | $0.01247 |
| Opus 5 | $0.00011 | $0.00624 |
| Sonnet 5 | $0.00004 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
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 11d 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 — 142 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 multi-channel marketing campaign plan ready for execution. Covers strategic objectives, audience segmentation, channel selection, budget distribution, phased timeline, content calendar, and measurable KPIs.
Trigger
User runs /digital-marketing-pro:campaign-plan or asks to plan, design, build, or launch a marketing campaign.
Inputs
Gather the following from the user. If not provided, ask before proceeding:
-
Campaign goal — the primary objective (drive signups, increase awareness, launch a product, generate leads, re-engage churned users, drive event registrations)
-
Product or service — what is being promoted
-
Target audience — who the campaign is aimed at (demographics, roles, industries, pain points, buying stage). If a brand profile exists, reference existing personas.
-
Timeline — campaign duration and any fixed dates (launch date, event, 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):
- Key differentiators or value propositions
- Previous campaign performance or learnings
- Geographic focus or market
- Channel constraints or preferences
- Compliance requirements
Brand Context
If a brand profile exists at ~/.claude-marketing/brands/, load it automatically:
- Apply brand voice settings to all messaging recommendations
- Reference existing audience personas instead of asking for them again
- Check for guidelines, restrictions, and compliance rules
- Load custom templates if available
- Check agency SOPs for campaign planning standards
If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with general best practices.
Campaign Brief Structure
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.
- 11d ago First seen · 142 lines · 22 tokens per session scan A f1ce63aa1f5f
campaign-plan is a command published in the GitHub repository indranilbanerjee/digital-marketing-pro (806 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 1,247 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-30.
Other commands, from other repositories
brand-setup
Configure brand voice, terminology, compliance guardrails, and style guide for content production.
output-folder
Print the absolute path to the user-visible ContentForge output folder and open it in the OS file manager.
create-content
Run the full 10-phase content production pipeline — research, draft, fact-check, humanize, and publish.
audit-content
Audit your content library for freshness decay, coverage gaps, and optimization opportunities.
content-brief
Generate a research-backed content brief with keyword data, competitor analysis, search intent, and SEO strategy.
publish
Publish finished content to Webflow or WordPress with preview, verification, and HTML export fallback.