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 product-launchgit 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/product-launch)<a href="https://agentmods.dev/skills/cbrock84/headcount/product-launch"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/product-launch/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/product-launch"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/product-launch.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.00096 | $0.00910 |
| Opus 5.5 | $0.00038 | $0.00364 |
| Sonnet 5.5 | $0.00019 | $0.00182 |
| Haiku 4.5 | $0.00010 | $0.00091 |
Grade A, and why
product-launch 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product launch
A launch is not an announcement. The announcement is the cheapest part and the part most likely to be mistaken for the whole thing, which is how features get press coverage and no adoption.
Tier the launch before planning it
Not everything deserves the same treatment, and treating everything as major is how a team burns its own attention and its audience's.
- Tier one — changes the story you tell about the product, or opens a new segment. Full motion: positioning work, press, sales enablement, customer communication, campaign.
- Tier two — meaningful to existing customers, not a new story. In-product announcement, documentation, a note to affected accounts, sales briefing.
- Tier three — improvement. Release notes and nothing else.
Agree the tier before work starts, and expect the pull toward tier one from whoever built it. Effort spent above the tier is taken from somewhere else, usually from the next launch.
Sequence internal readiness ahead of the announcement
The order matters and gets reversed constantly. Support and sales find out from the announcement, then spend launch week answering questions they were never briefed on, badly.
Before anything external: documentation exists, support can answer the top questions, sales knows who it is for and who it is not for, pricing and packaging are decided and configured, and the thing works for the accounts that will try it first.
Have someone outside the team use it from scratch. The team cannot see the first-run experience any more, and the first-run experience is what everyone else gets.
Decide who it is for, and say who it is not for
A launch aimed at everyone lands on no one. Name the segment, the problem it solves, and what changes for them — and say explicitly who should not use it yet. Sales will otherwise sell it to whoever asks, and the earliest customers will be the worst-fit ones.
Pick a date for a reason, and defend the criteria over the date
Launch dates get set by an event, a quarter, or a promise. Whatever fixes it, write down the criteria that must hold to launch on it — quality bar, documentation, support readiness — and treat those as the real gate.
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 20f2d212c8af
- 1mo ago First seen · 75 lines · 96 tokens per session scan A c3f2f98d6809
product-launch is a skill published in the GitHub repository cbrock84/headcount (2,077 stars, last pushed 2d ago), licensed MIT. It adds 96 tokens to every session and 910 once invoked, about $0.0004 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
user-story-map
Build an interactive, drag-and-drop user story map so the user can re-slice work across release phases. Use when the user wants a story map, a phased roadmap, release slicing, a backbone/activities journey map, or to decide "which stories go in which phase" and move them around.
agile-ledger
Plain-Markdown Scrum / Agile product-management system for Claude Code. Manage a product backlog of Epics and User Stories, plan and run sprints, drive a board, track velocity, cut Major.Minor releases, and keep GitHub branches/commits/PRs traceable to stories — all from slash commands, with no Jira and no database.…
agile-ledger-workspace
Owns the Agile-Ledger ledger repository — the separate repo that holds one folder per code repo, so code repos stay clean. Create the ledger repo, register repositories into it, migrate a pre-2.0 in-repo Agile-Ledger/ folder, discover repositories on a GitHub org (including ones nobody told you about), run a single…
people-integration
Design the first 90 days for acquired product talent so they stay, contribute, and feel ownership. Produces decision map session template, mentor pairing matrix, 30/60/90 ownership plan, retention risk review (purpose and influence), and 1:1 coaching question library.
roadmap-convergence
Facilitate the post-acquisition roadmap convergence process across Weeks 1 to 8. Produces the conflict log, three-session facilitation guides, merged 90-day plus 12-month roadmap, and the 30/60/90 execution plan.
week-0-readiness
Run a product leader through pre-close (Week 0) integration readiness for an acquisition. Produces the integration lead charter, decision rights one-pager, combined product narrative draft, customer commitment inventory, and the five-question Day 1 readiness check.