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 indranilbanerjee/neels-plugins --skill campaign-plangit clone --depth 1 https://github.com/indranilbanerjee/neels-pluginsWrote 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/indranilbanerjee/neels-plugins/campaign-plan)<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/campaign-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/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.
<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/campaign-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/campaign-plan.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.00815 |
| Opus 5.5 | $0.00012 | $0.00326 |
| Sonnet 5.5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
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 2d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:campaign-plan
Purpose
Generate a comprehensive multi-channel campaign plan ready for execution. Covers strategic objectives, audience segmentation, channel selection, budget distribution, phased timeline, and measurable KPIs.
Input Required
The user must provide (or will be prompted for):
- Campaign goal: What the campaign should achieve (awareness, leads, sales, retention, etc.)
- Product/service: What is being promoted
- Target audience: Who the campaign is for (or use existing brand personas)
- Budget: Total available budget or budget range
- Timeline: Campaign duration or key dates (launch, event, season)
- Constraints: Any channel restrictions, compliance requirements, or creative limitations
Process
- Load brand context: Read
~/.claude-marketing/brands/_active-brand.jsonfor the active slug, then load~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at~/.claude-marketing/brands/{slug}/guidelines/_manifest.json— if present, load restrictions and relevant category files. Check for custom templates at~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. - Load shared planning references (don't re-derive them): Consume the campaign-orchestrator reference docs rather than duplicating their frameworks —
skills/campaign-orchestrator/campaign-planning.md(planning framework),skills/campaign-orchestrator/channel-strategy.md(channel selection),skills/campaign-orchestrator/budget-allocation.md(budget-split heuristics),skills/campaign-orchestrator/utm-tracking.md(UTM naming conventions), andskills/campaign-orchestrator/abm-strategy.md(ABM). This skill produces the plan document;/digital-marketing-pro:campaign-orchestratorruns the broader multi-agent orchestration on top of the same references. - Clarify campaign objective and classify as awareness, consideration, or conversion
- Define primary and secondary audience segments with targeting parameters
- Recommend channel mix based on audience behavior, budget, and objective
- Allocate budget across channels using expected CPM/CPC benchmarks for the industry
- Build a phased timeline: pre-launch, launch, sustain, optimize, wrap-up
- Define KPIs per channel and overall campaign success metrics
- Identify dependencies, risks, and contingency actions
- Output the full plan in a structured, actionable format
What ships with it
2 files 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.
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.
- 2d ago First seen · 55 lines · 30 tokens per session scan A cff6c1019433
campaign-plan is a skill published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 815 once invoked, about $0.0001 per session on Opus 5.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-10-12.
Other skills, from other repositories
continuous-improvement-loop
Run the Part 12 continuous improvement loop into a quarterly brief for leadership. "produce the quarterly improvement brief".
yearly-planner
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. "plan the whole year month by month".
attribution-report
Run attribution on real conversion paths, comparing models. "which channels actually drive revenue".
validate-output
Validate content structure against a schema: sections, word counts. "scan for leftover placeholders".
add-integration
Add a custom MCP integration: scaffold the server, write .mcp.json, test it. "add a new MCP server".
client-proposal
Draft a client proposal or RFP response: scope, deliverables, KPIs, pricing tiers. "respond to this RFP".