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.
npx skills add cogni-work/insight-wave --skill campaign-buildergit clone --depth 1 https://github.com/cogni-work/insight-waveWrote 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.
[](https://agentmods.dev/skills/cogni-work/insight-wave/campaign-builder)<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>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.
| Model | Per session | Once 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 |
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.
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
- Read
content-strategy.jsonfor this market × GTM path - Scan
content/directories for existing pieces matching this cell - 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:
-
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.
-
Audience: Primary persona from portfolio customer profiles
-
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.
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.
- 3d ago First seen · 179 lines · 87 tokens per session scan A b685e5d58820
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…