campaign-plan

A marketing campaign planning guide that turns a goal into a brief covering the audience, message, channels, content schedule, and measures of success.

In plain words
What is it for?
Use it to plan product launches, lead-generation efforts, or awareness campaigns, including week-by-week content schedules.
Why use it?
It removes the need to assemble a campaign plan from scattered decisions and helps expose missing details such as the target audience, timing, or budget.

Skill for Claude CodeCodex

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/xyruscode/ai-sync/campaign-plan
Any agent
npx skills add XyrusCode/ai-sync --skill campaign-plan
Clone the repo
git clone --depth 1 https://github.com/XyrusCode/ai-sync

Made for: Claude Code, Codex.

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,084 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00065 $0.03084
Opus 5 $0.00032 $0.01542
Sonnet 5 $0.00013 $0.00617
Haiku 4.5 $0.00006 $0.00308

Measured yesterday against content hash b050b7098375, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

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.

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

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

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. yesterday First seen · 310 lines · 65 tokens per session scan A b050b7098375

Subscribe to this mod's changes

campaign-plan is a skill published in the GitHub repository XyrusCode/ai-sync (2 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 3,084 once invoked, about $0.0003 per session on Opus 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

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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens