campaign-plan

campaign-plan is a skill for Claude Code from Mora-AI-Content-Studio/mora-claude-plugin. It costs 42 tokens per session (546 once invoked), scanned A, original, MIT.

A campaign-planning workflow for Mora AI, a platform for planning, drafting, approving, and scheduling social content.

In plain words
What is it for?
It creates launch plans, marketing directions, editorial calendars, and recommendations for what content to create next.
Why use it?
It bases the proposed plan on the account's brand, existing work, audiences, content themes, and past performance instead of generic advice.

Skill for Claude Code

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

Part of the mora plugin — 6 skills, 1 MCP server shipped together

Good fit It creates launch plans, marketing directions, editorial calendars, and recommendations for what content to create next.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mora-ai-content-studio/mora-claude-plugin/campaign-plan
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.

Any agent
npx skills add Mora-AI-Content-Studio/mora-claude-plugin --skill campaign-plan
Clone the repo
git clone --depth 1 https://github.com/Mora-AI-Content-Studio/mora-claude-plugin

Made for: Claude Code.

Or install mora, the plugin that ships this one along with the rest of its 6 skills, 1 MCP server.

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/mora-ai-content-studio/mora-claude-plugin/campaign-plan/github.svg)](https://agentmods.dev/skills/mora-ai-content-studio/mora-claude-plugin/campaign-plan)
Your own site
<a href="https://agentmods.dev/skills/mora-ai-content-studio/mora-claude-plugin/campaign-plan"><img src="https://agentmods.dev/badge/skills/mora-ai-content-studio/mora-claude-plugin/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/mora-ai-content-studio/mora-claude-plugin/campaign-plan"><img src="https://agentmods.dev/badge/skills/mora-ai-content-studio/mora-claude-plugin/campaign-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 546 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 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.00042 $0.00546
Opus 5 $0.00021 $0.00273
Sonnet 5 $0.00008 $0.00109
Haiku 4.5 $0.00004 $0.00055

Measured 10d ago against content hash 261cd9d5407d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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.

skills/campaign-plan/SKILL.md · 44 lines

How it starts

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

Campaign Plan

Create a campaign plan from the user's real Mora AI context. This skill creates a proposed plan in the conversation; it does not create projects, schedule posts, publish content, set ad budgets, or change any account state.

When to use this

Use for a launch plan, content calendar, campaign direction, or a request to decide what to create next. Do not use it for a single piece of copy, a performance audit, or checking whether an existing plan was executed. Route those requests to paid-ad-copy, content-performance-audit, or content-gap-check.

Procedure

  1. Call get_brand_profile first. Use it as the factual baseline for the business, voice, audience, and offerings.
  2. Call list_projects and list_posts to understand commitments already planned, drafted, scheduled, and published. Do not propose a calendar that silently duplicates active work.
  3. Call list_audiences and list_content_angles to choose a target audience and a small set of grounded messages. If those results are thin, identify the missing context instead of inventing personas or pain language.
  4. Call get_post_performance when there is published-history data. Use it to prioritize proven themes or formats, but do not claim it establishes causation.
  5. Call list_products only when the campaign needs catalogue facts. Use returned product names, prices, and descriptions exactly; an empty result means no connected catalogue context is available.
  6. Ask for the campaign objective, time horizon, primary platform, offer, and CTA when they are not supplied. State any assumptions that remain after the question.
  7. Produce a plan with a specific objective, audience, angle sequence, content inventory, cadence, CTA logic, evidence used, and open decisions. Separate recommended organic posts from paid-ad variants; the public connection can draft copy but cannot create or manage campaigns.

Quality bar

  • Every recommendation must trace to account data, a user-provided goal, or a clearly labeled assumption.
  • Do not use a scheduled post as evidence that it was published or performed.
  • Do not invent a product, offer, price, audience, metric, landing page, or platform capability.
  • Keep the plan useful to a human operator: a concise table or ordered sequence is better than generic campaign language.

Read the full file on GitHub · 44 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. 10d ago First seen · 44 lines · 42 tokens per session scan A 261cd9d5407d

Subscribe to this mod's changes

campaign-plan is a skill published in the GitHub repository Mora-AI-Content-Studio/mora-claude-plugin (0 stars, last pushed 19d ago), licensed MIT. It adds 42 tokens to every session and 546 once invoked, about $0.0002 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-31.

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

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

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

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

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens