campaign-planning

campaign-planning is a skill for Claude Code from fergupa/claude_plugins. It costs 50 tokens per session (2,211 once invoked), scanned A, original, Apache-2.0.

A planning framework for marketing campaigns, covering the goal, target audience, message, channels, content schedule, budget, and success measures.

In plain words
What is it for?
Use it to plan product launches, content calendars, audience segments, channel choices, budgets, and campaign KPIs, or key performance indicators.
Why use it?
It helps turn a broad campaign idea into an organized plan with clear outcomes and ways to measure progress.

Skill for Claude Code

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

Part of the marketing plugin — 5 skills, 7 commands shipped together

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.

agentmods
npx agentmods add skills/fergupa/claude_plugins/campaign-planning
Any agent
npx skills add fergupa/claude_plugins --skill campaign-planning
Clone the repo
git clone --depth 1 https://github.com/fergupa/claude_plugins

Made for: Claude Code.

Or install marketing, the plugin that ships this one along with the rest of its 5 skills, 7 commands.

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-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/fergupa/claude_plugins/campaign-planning.svg)](https://agentmods.dev/skills/fergupa/claude_plugins/campaign-planning)
Your own site
<a href="https://agentmods.dev/skills/fergupa/claude_plugins/campaign-planning"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/campaign-planning.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,211 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00050 $0.02211
Opus 5 $0.00025 $0.01105
Sonnet 5 $0.00010 $0.00442
Haiku 4.5 $0.00005 $0.00221

Measured 2d ago against content hash bd42e411831e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

campaign-planning 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 2d 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.

marketing/skills/campaign-planning/SKILL.md · 203 lines

How it starts

The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Campaign Planning Skill

Frameworks and guidance for planning, structuring, and executing marketing campaigns.

Campaign Framework: Objective, Audience, Message, Channel, Measure

Every campaign should be built on this five-part framework:

1. Objective

Define what success looks like before planning anything else.

  • Awareness: increase brand or product visibility (measured by reach, impressions, share of voice)
  • Consideration: drive engagement and education (measured by content engagement, email signups, webinar attendance)
  • Conversion: generate leads or sales (measured by signups, demos, purchases, pipeline)
  • Retention: re-engage existing customers (measured by churn reduction, upsell, NPS)
  • Advocacy: turn customers into promoters (measured by referrals, reviews, UGC)

Good objectives are SMART: Specific, Measurable, Achievable, Relevant, Time-bound.

Example: "Generate 200 marketing qualified leads from mid-market SaaS companies in North America within 6 weeks of campaign launch."

2. Audience

Define who you are trying to reach with enough specificity to guide messaging and channel decisions.

  • Demographics: role/title, seniority, company size, industry
  • Psychographics: motivations, pain points, goals, objections
  • Behavioral: where they consume content, how they buy, what they have engaged with before
  • Buying stage: are they unaware of the problem, researching solutions, or ready to buy?

Create a brief audience profile (not a full persona) for campaign planning:

"[Role] at [company type] who is struggling with [pain point] and looking for [desired outcome]. They typically discover solutions through [channels] and care most about [priorities]."

3. Message

Craft the core message and supporting points that will resonate with the audience.

  • Core message: one sentence that captures what you want the audience to think, feel, or do
  • Supporting messages: 3-4 points that provide evidence, address objections, or elaborate on benefits
  • Proof points: data, case studies, testimonials, or third-party validation for each supporting message
  • Differentiation: what makes your offering different from alternatives (including doing nothing)

Read the full file on GitHub · 203 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. 2d ago First seen · 203 lines · 50 tokens per session scan A bd42e411831e

Subscribe to this mod's changes

campaign-planning is a skill published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,211 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 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

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