campaign-builder

campaign-builder is a skill for Claude Code from cogni-work/insight-wave. It costs 87 tokens per session (1,710 once invoked), scanned A, original, Apache-2.0.

A campaign-planning skill that coordinates existing and new content across several channels on a day-by-day timeline.

In plain words
What is it for?
It helps build a timed campaign for one market and one go-to-market path, with touchpoints and objectives.
Why use it?
It brings separate content pieces into one organised campaign and highlights planned pieces that are still missing.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the cogni-marketing plugin — 11 skills, 11 commands, 3 agents shipped together

Good fit It helps build a timed campaign for one market and one go-to-market…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cogni-work/insight-wave/campaign-builder
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 cogni-work/insight-wave --skill campaign-builder
Clone the repo
git clone --depth 1 https://github.com/cogni-work/insight-wave

Made for: Claude Code.

Or install cogni-marketing, the plugin that ships this one along with the rest of its 11 skills, 11 commands, 3 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/cogni-work/insight-wave/campaign-builder.svg)](https://agentmods.dev/skills/cogni-work/insight-wave/campaign-builder)
Your own site
<a href="https://agentmods.dev/skills/cogni-work/insight-wave/campaign-builder"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/campaign-builder.svg" alt="Measured on agentmods" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,710 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.00087 $0.01710
Opus 5 $0.00044 $0.00855
Sonnet 5 $0.00017 $0.00342
Haiku 4.5 $0.00009 $0.00171

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

Security

Grade A, and why

campaign-builder 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 3d 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.

cogni-marketing/skills/campaign-builder/SKILL.md · 179 lines

How it starts

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

Campaign Builder

Purpose

Orchestrate existing and new content pieces into a coordinated multi-channel campaign with day-based timing, touch sequences, and clear objectives. One campaign = one market × one GTM path. Cross-path campaigns are built by combining multiple campaign objects.

Prerequisites

  • Marketing project with content strategy defined
  • Recommended: some content already generated (the campaign assembles + fills gaps)

Input Parameters

Parameter Required Description
market Yes Market slug
gtm_path Yes GTM path theme ID
campaign_name No Campaign name (kebab-case). If omitted, derive from theme
duration_weeks No Campaign duration (default: 8 weeks)

Workflow

Step 1: Load Existing Content

  1. Read content-strategy.json for this market × GTM path
  2. Scan content/ directories for existing pieces matching this cell
  3. Identify gaps — what's planned but not yet generated

Present inventory:

Campaign: {gtm_path} in {market}
Existing content:
  ✅ thought-leadership/blog (1050w, draft)
  ✅ demand-generation/linkedin-post-01 (280w, draft)
  ✅ demand-generation/linkedin-post-02 (250w, draft)
  ❌ lead-generation/whitepaper — NOT YET GENERATED
  ❌ lead-generation/landing-page — NOT YET GENERATED
  ❌ sales-enablement/battle-card — NOT YET GENERATED

Would you like me to generate the missing pieces first, or build the campaign with what we have?

Step 2: Campaign Architecture

Define campaign structure:

  1. Objective: What this campaign aims to achieve

    • Awareness-focused: reach, impressions, engagement rate
    • Lead-focused: MQLs, whitepaper downloads, webinar registrations
    • Pipeline-focused: demos booked, proposals sent Recommend based on funnel focus from content strategy.
  2. Audience: Primary persona from portfolio customer profiles

  3. Phases (map to funnel):

    • Phase 1 — Attract (weeks 1-2): Thought leadership + social. Build awareness.
    • Phase 2 — Engage (weeks 3-5): Deep content + email. Drive consideration.
    • Phase 3 — Convert (weeks 6-8): Gated assets + sales follow-up. Capture leads.

Read the full file on GitHub · 179 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. 3d ago First seen · 179 lines · 87 tokens per session scan A b685e5d58820

Subscribe to this mod's changes

campaign-builder is a skill published in the GitHub repository cogni-work/insight-wave (12 stars, last pushed today), licensed Apache-2.0. It adds 87 tokens to every session and 1,710 once invoked, about $0.0004 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-04.

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

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

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

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