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 activationgit 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/activation)<a href="https://agentmods.dev/skills/cbrock84/headcount/activation"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/activation/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/activation"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/activation.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.00074 | $0.00726 |
| Opus 5.5 | $0.00030 | $0.00290 |
| Sonnet 5.5 | $0.00015 | $0.00145 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
activation 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activation
Acquisition spend is wasted downstream of a weak activation. This is usually the cheapest place to improve revenue and the least worked on.
Define the activation moment
Name the specific thing a new user does that predicts they will stay — not "logged in twice," but the action that delivers the value they came for. Find it in the data: compare what retained users did in week one against what churned users did.
Everything in onboarding exists to get people to that moment faster. Without it defined, onboarding becomes a feature tour.
Signup
Every field costs conversion, and each one must earn its place. Ask for what is needed to deliver value now; collect the rest later, in context, when the reason is obvious.
- Defer email verification past first value where the product allows it.
- Never ask for payment details before value is delivered unless the model requires it.
- Show progress on multi-step flows, and let people finish later without losing work.
- Errors inline and specific. A form that rejects on submit without saying which field is where people leave.
Onboarding
The goal is the first real outcome, not a completed tour.
- Use their data, not sample data. The moment someone sees their own information in the product is the moment it becomes real.
- One action at a time, each visibly advancing toward the outcome.
- Skippable, resumable, and repeatable. Forced linear onboarding fails everyone whose situation differs from the assumed one.
- Empty states do the teaching. They are the most-seen screens in a new account and usually the least designed.
Checklists work when the items lead to real value and the list can be dismissed. They fail when they are busywork.
Diagnosing
Instrument each step and find the largest drop. Then watch session recordings of people who dropped there — the quantitative data says where, and only observation says why.
Common causes, in rough order: asked for too much too early, value not visible before effort required, an empty product with no path out of it, and a required integration nobody has permissions for.
What ships with it
1 file 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.
- 1mo ago Changed · +7 lines 5f3ff5e6347c
- 1mo ago First seen · 66 lines · 74 tokens per session scan A bdfd93459184
activation is a skill published in the GitHub repository cbrock84/headcount (2,077 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 726 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
rotate-creative
Pause fatigued ads and ship fresh creative variants in their place. Works on both Meta and Google Ads. Use when CTR is dropping, frequency is climbing, or the user says "creative is tired" / "let's refresh ads". Always starts new variants paused.
launch-google-search
Launch a complete Google Ads Search campaign — campaign, ad group, responsive search ads, keywords, sitelinks, callouts, and negatives — built paused and ready to review. Use when the user wants to spin up a new Search campaign on Google Ads.
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.
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.
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…