campaign-plan

campaign-plan is a skill for Claude Code from charlieviettq/awesome-agent-skill. It costs 65 tokens per session (3,055 once invoked), scanned A, a copy of campaign-plan, MIT.

A planning tool for marketing campaigns that turns a goal into an audience, message, channel plan, content calendar, timeline, and success measures. It can cover product launches, lead generation, and awareness campaigns.

In plain words
What is it for?
Use it to plan campaigns, choose channels, schedule content week by week, define target customers, set objectives, and decide how results will be measured.
Why use it?
It connects scattered marketing decisions into one working plan. This makes dependencies, timing, budget considerations, and measures of success easier to see.

Skill for Claude Code

Written for Claude Code: allowed-tools 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-marketing.md)..

Good fit Use it to plan campaigns, choose channels, schedule content week by week, define target customers, set objectives, and decide how results will be measured.

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/charlieviettq/awesome-agent-skill
agentmods
npx agentmods add skills/charlieviettq/awesome-agent-skill/campaign-plan

Made for: Claude Code.

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/charlieviettq/awesome-agent-skill/campaign-plan/github.svg)](https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/campaign-plan)
Your own site
<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/campaign-plan"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/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/charlieviettq/awesome-agent-skill/campaign-plan"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/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,055 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 95% 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.03055
Opus 5.5 $0.00026 $0.01222
Sonnet 5.5 $0.00013 $0.00611
Haiku 4.5 $0.00006 $0.00305

Measured 1mo ago against content hash c78b8ec4777a, 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 1mo 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

95% identical to campaign-plan — 7 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.

.claude/skills/campaign-plan/SKILL.md · 310 lines

How it starts

The opening of the file, as written. The whole thing — 310 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 · 310 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. 1mo ago First seen · 310 lines · 65 tokens per session scan A c78b8ec4777a

Subscribe to this mod's changes

campaign-plan is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 3,055 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to campaign-plan, differing in 7 lines, and is treated as a copy.

Related

Other skills, from other repositories

tool-calling-tutor

Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.

WenyuChiou/awesome-agentic-ai-zh · 62 tokens

dep-auditor

A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.

laolaoshiren/claude-code-skills-zh · 72 tokens

skill-curator

A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.

laolaoshiren/claude-code-skills-zh · 75 tokens

api-tester

A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.

laolaoshiren/claude-code-skills-zh · 86 tokens

env-manager

An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.

laolaoshiren/claude-code-skills-zh · 22 tokens

eslint-fix

A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.

laolaoshiren/claude-code-skills-zh · 79 tokens