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 pricing-and-packaginggit 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/pricing-and-packaging)<a href="https://agentmods.dev/skills/cbrock84/headcount/pricing-and-packaging"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/pricing-and-packaging/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/pricing-and-packaging"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/pricing-and-packaging.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.00073 | $0.00705 |
| Opus 5.5 | $0.00029 | $0.00282 |
| Sonnet 5.5 | $0.00015 | $0.00141 |
| Haiku 4.5 | $0.00007 | $0.00071 |
Grade A, and why
pricing-and-packaging 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing and packaging
The highest-leverage number in the business and the least examined. Most companies are underpriced and have never tested it.
The pricing metric
Choose what you charge per before choosing how much. It should scale with the value the customer receives, be predictable enough to budget, and be something they cannot easily game.
Get this wrong and no amount of tuning the number fixes it — a metric that scales with your cost rather than their value creates a permanent argument at every renewal.
Setting the level
Anchor on value delivered, not cost incurred. Cost sets a floor and nothing else.
Evidence to gather: what the alternative costs them today including labor, what similar categories charge, and what current customers say about price — with the caveat that nobody says a price is too low. Willingness-to-pay research is directional, not decisive; people misreport.
If nobody ever objects to your price, it is too low. Some loss on price is correct.
Packaging
Tiers should map to distinguishable segments with different needs, not to arbitrary feature counts. Three is usually right; more creates paralysis and support load.
Each tier needs one obvious reason to upgrade, tied to something that grows with the customer's success. Gating on a feature they will never need does not drive upgrades; gating on a limit they will hit does.
Name tiers for who they are for, not by metal. "Team" and "Business" tell a buyer where they belong.
Monetization surfaces
Upgrade prompts and paywalls should appear at the moment of blocked value — when someone is trying to do the thing the tier does not allow, not on a schedule.
Explain what is behind the gate and why the limit exists. An unexplained wall reads as extraction. Show the value already received before asking for payment, and make declining easy — dark patterns buy one conversion and lose the account.
Changing price
- Grandfather existing customers, or expect churn well beyond the price-sensitive segment.
- Announce with real notice and a clear reason.
- Change one thing at a time — price and packaging together makes the result unreadable.
- Model the downside first: at what churn rate does this increase lose money?
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 2a839f7b883d
- 1mo ago First seen · 62 lines · 73 tokens per session scan A f4289fe4dd78
pricing-and-packaging is a skill published in the GitHub repository cbrock84/headcount (2,077 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 705 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
launch-pmax
Launch a Google Ads Performance Max campaign with a complete asset group, audience signals, and (for ecom) listing groups. Built paused for review. Use when the user wants a new PMax campaign.
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.
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…