campaign-plan

campaign-plan is a skill for Claude Code from sun2443/designer-skills. It costs 65 tokens per session (3,042 once invoked), scanned A, a copy of campaign-plan, Apache-2.0.

A marketing campaign planning workflow that turns a goal into a brief covering the audience, message, channels, schedule, and success measures. A campaign is a coordinated set of promotional activities over a defined period.

In plain words
What is it for?
Planning product launches, lead-generation efforts, awareness campaigns, channel strategies, content calendars, and campaign metrics.
Why use it?
It helps replace an unclear marketing goal with an organised plan, including a week-by-week content schedule and dependencies.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md)..

Part of the marketing plugin — 8 skills shipped together

Good fit Planning product launches, lead-generation efforts, awareness campaigns, channel strategies, content calendars, and campaign metrics.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/sun2443/designer-skills
agentmods
npx agentmods add skills/sun2443/designer-skills/campaign-plan

Made for: Claude Code.

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

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

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

agentmods 80×15 button for campaign-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/sun2443/designer-skills/campaign-plan"><img src="https://agentmods.dev/badge/skills/sun2443/designer-skills/campaign-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,042 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 100% copy Near-identical to another mod 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.00065 $0.03042
Opus 5.5 $0.00026 $0.01217
Sonnet 5.5 $0.00013 $0.00608
Haiku 4.5 $0.00006 $0.00304

Measured 13d ago against content hash f0b146074b64, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 13d 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.

Origin

This is a copy

100% identical to campaign-plan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

marketing/skills/campaign-plan/SKILL.md · 309 lines

How it starts

The opening of the file, as written. The whole thing — 309 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:

  1. Campaign goal — the primary objective (e.g., drive signups, increase awareness, launch a product, generate leads, re-engage churned users)

  2. Target audience — who the campaign is aimed at (demographics, roles, industries, pain points, buying stage)

  3. Timeline — campaign duration and any fixed dates (launch date, event date, seasonal deadline)

  4. Budget range — approximate budget or budget tier (optional; if not provided, generate a channel-agnostic plan and note where budget allocation would matter)

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

Read the full file on GitHub · 309 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. 13d ago First seen · 309 lines · 65 tokens per session scan A f0b146074b64

Subscribe to this mod's changes

campaign-plan is a skill published in the GitHub repository sun2443/designer-skills (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 65 tokens to every session and 3,042 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to campaign-plan, differing in 0 lines, and is treated as a copy.

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