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-planninggit 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-planning)<a href="https://agentmods.dev/skills/cbrock84/headcount/marketing-planning"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/marketing-planning/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-planning"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/marketing-planning.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.00066 | $0.00493 |
| Opus 5 | $0.00033 | $0.00246 |
| Sonnet 5 | $0.00013 | $0.00099 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
marketing-planning 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 5d 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.
What it actually says
Marketing planning
Start from the constraint, not the calendar
Name the single thing limiting growth right now: not enough people know, not enough of the right people know, they know but do not believe, they believe but do not act, or they act but do not stay. Each implies a different plan. A plan that funds all five funds none properly.
Structure
- Objective — one primary number with a date. Supporting metrics are supporting.
- The constraint and the evidence for it.
- Segments — who, in priority order, and who is explicitly out of scope this period.
- Channel mix — three tiers:
- Proven — working now; fund to capacity, then stop. Most channels have a ceiling and spending past it buys worse customers.
- Scaling — evidence but not yet at capacity; the growth budget.
- Experimental — capped at a share you can lose entirely without missing the objective.
- Sequencing — what has to be true before each thing starts. Content before paid, positioning before content.
- Budget — by tier and channel, with the fixed-versus-variable split visible.
- Measurement — the leading indicator per channel and when it should first move. A channel with no stated read-by date runs forever.
- Kill criteria — what result stops each experiment. Decided in advance, when it is cheap.
Pressure-test before committing
- What must be true for this to work, and which of those is least certain?
- What happens at half the budget? If the plan collapses, it has no core.
- Which line item would you cut first? If nothing, the plan is not prioritized.
- Where does this depend on another team delivering, and have they agreed?
Never
- Plan channel activity before positioning is settled.
- Fund an experiment you cannot afford to have fail.
- Report a plan without stating what did not get funded and why.
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.
- 5d ago First seen · 43 lines · 66 tokens per session scan A 293254712875
marketing-planning is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 6d ago), licensed MIT. It adds 66 tokens to every session and 493 once invoked, about $0.0003 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.
dns
This skill should be used when the user asks about "DNS", "domain resolution", "GeoDNS / geo routing", "latency-based routing", "weighted / failover routing", "Route 53 / Cloud DNS", an "A/CNAME/ALIAS record", "anycast", or "DNS TTL / propagation". It gives the global front door that maps a name to the right IP and…