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 benefits-realizationgit 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/benefits-realization)<a href="https://agentmods.dev/skills/cbrock84/headcount/benefits-realization"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/benefits-realization.svg" alt="Measured on agentmods" 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.00067 | $0.00639 |
| Opus 5 | $0.00034 | $0.00319 |
| Sonnet 5 | $0.00013 | $0.00128 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
benefits-realization 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 3d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benefits realization
Projects are approved on promised benefits and closed on delivered scope. The gap between those two sentences is why organizations repeat expensive mistakes with confidence.
Define benefits so they can be disproved
A benefit that cannot fail to be claimed is not a benefit. Each needs a measure, a current baseline, a target, a date by which it should appear, and an owner who is accountable after the project closes — usually the operational owner, not the project manager, who has moved on.
Distinguish honestly:
- Cashable — the budget actually reduces. Someone can point at the line.
- Non-cashable — time is released. Real, but only becomes value if that time is redeployed to something that matters, which is a separate management act nobody schedules.
- Cost avoidance — a future cost does not occur. Legitimate and unverifiable, so treat claims sceptically.
- Non-financial — risk reduction, compliance, experience. Often the actual reason. Say so rather than manufacturing a financial number nobody believes.
The most common failure is a business case padded with non-cashable savings presented as though the budget will fall. It will not, and the credibility loss lands on the next case.
Baseline before you change anything
A baseline captured after go-live is not a baseline. Measure first, and record how it was measured — by the time anyone checks, the method will be disputed and nobody will remember.
Tracking happens after the project ends
Benefits appear months after delivery, when the project team has dispersed and attention has moved. This is precisely why it does not happen, and why it needs to be owned by the operational line and scheduled at approval rather than intended.
Set review points at meaningful intervals — ninety days, six months, a year — and hold them regardless of what the answer looks like.
Post-implementation review worth the hour
Two questions: did the benefits appear, and would we make the same decision knowing what we now know?
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.
- 3d ago First seen · 62 lines · 67 tokens per session scan A c1e0cddac7bb
benefits-realization is a skill published in the GitHub repository cbrock84/headcount (1,300 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 639 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
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
Optional multi-repo orchestrator for Agile-Ledger. Install once at a workspace root to manage many repositories at once: discover new repositories on a GitHub org (including ones nobody told you about), clone and bootstrap them, run a single cross-repo "what changed while I was away" sync, and reconstruct undocumented…
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.