headcount is an organization of independently installable Claude Code plugins, each grouping skills for a department such as finance, security, or demand generation. Claude Code users install the departments they need and invoke their skills for specialized work; the catalogue entries are skills and related agent tooling from that organization.
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 cbrock84/headcount --skill marketing-campaign-plannergit clone --depth 1 https://github.com/cbrock84/headcountWrote 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/cbrock84/headcount/marketing-campaign-planner)<a href="https://agentmods.dev/skills/cbrock84/headcount/marketing-campaign-planner"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/marketing-campaign-planner/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/cbrock84/headcount/marketing-campaign-planner"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/marketing-campaign-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00093 | $0.00975 |
| Opus 5 | $0.00046 | $0.00487 |
| Sonnet 5 | $0.00019 | $0.00195 |
| Haiku 4.5 | $0.00009 | $0.00097 |
Grade A, and why
marketing-campaign-planner 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 8d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing campaign planner
A campaign is a bounded push around one story. If it has no end date and no single story, it is a program, not a campaign, and it should be planned as one.
One story
Every campaign carries exactly one idea. Channels change the format; they never change the meaning. Campaigns that say slightly different things on each channel produce no compounding — the audience sees three impressions and remembers none.
Write the story as a sentence before anything else: for whom, what changes, why now. If it takes a paragraph, it is not ready and the campaign will not hold.
The "why now" is the part most campaigns skip and the part that produces urgency. Without it you are asking people to act on something that would be equally true next quarter.
Objective
One primary number with a date, and the leading indicator that will move first. Campaigns with several equal objectives cannot be sequenced, because every tradeoff has an argument on both sides.
State what you are not optimizing for. A launch optimizing for signups will make choices that cost brand, and that is fine — as long as it was chosen.
Channels: choose, do not spray
Pick channels by where the audience already is and which formats you can actually produce well. Two channels executed properly beat five done adequately, and the fifth channel usually consumes the attention that would have made the first two work.
Sequence them. Most campaigns run everything at once and learn nothing:
- Owned first — your list and existing audience. Cheapest, fastest signal, and it tells you whether the message lands before you pay to amplify it.
- Earned next — press, partners, communities. Needs lead time; brief them before launch.
- Paid last, amplifying what already worked. Paying to distribute an untested message is how budget disappears.
Timeline
Work backward from the launch date, and place the asset freeze at least several days before anything ships. Campaigns slip because copy is still being edited while ads are being trafficked.
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.
- 8d ago First seen · 95 lines · 93 tokens per session scan A e86c86656346
marketing-campaign-planner is a skill published in the GitHub repository cbrock84/headcount (1,356 stars, last pushed 9d ago), licensed MIT. It adds 93 tokens to every session and 975 once invoked, about $0.0005 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-03.
Other skills, from other repositories
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
mode
Show or set NeatContext routing to auto, ask, or manual for Codex, with an optional default shared with every other NeatContext host. Use only when the user explicitly invokes this skill or clearly asks to change routing behavior.
status
Report the NeatContext context and routing mode active in Codex, including missing-file or stale-routing warnings. Use when the user asks which context is connected or explicitly invokes this skill.
list
List the local NeatContext Contexts available to Codex. Use when the user asks what contexts exist, what can be connected, or explicitly invokes this skill.
build-oxpecker-web-app
Build or modify an Oxpecker web application in idiomatic F#, using endpoint routing, functional EndpointHandler and EndpointMiddleware composition, ASP.NET Core metadata, and focused endpoint tests.
go
Compatibility entry for Visual Stack's former /vstack:go command. Runs the wireframe and UI review tool, now called review. Use only when the user invokes /vstack:go.