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 program-managementgit 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/program-management)<a href="https://agentmods.dev/skills/cbrock84/headcount/program-management"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/program-management.svg" alt="Measured on agentmods" height="20"></a>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.00068 | $0.00560 |
| Opus 5 | $0.00034 | $0.00280 |
| Sonnet 5 | $0.00014 | $0.00112 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
program-management 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Program management
Programs fail at the seams between teams, not inside them. The job is the seams.
Set up
- One outcome, stated as a business result with a date. Programs with several equal objectives have none.
- A named accountable owner — one person, not a committee. The program manager drives; the owner decides.
- Scope written as inclusions and exclusions. The exclusions do the work; unwritten exclusions return as assumptions.
- Dependencies mapped and agreed by the teams that owe them, with dates they have actually committed to. A dependency in your plan that the owning team has not agreed to is a wish.
Sequencing
Order by dependency and risk, not by team convenience. Front-load the things that could invalidate the plan — the technical unknown, the vendor decision, the approval that might not come. Discovering in month four that the plan was impossible is the characteristic program failure.
Build in slack at integration points, not at the end. End-loaded buffer gets consumed early and silently.
Status that is worth reading
Three things, every time: are we on track for the date, what changed since last time, and what decision or unblock is needed. Everything else is appendix.
Track status against committed dates, not effort. "80% complete" is not information; "the integration is done, the migration starts Monday, the sign-off is the risk" is.
Escalate early and specifically. An escalation naming the decision needed and the date it is needed by gets resolved; a general statement of concern gets acknowledged and nothing happens.
When it slips
Establish whether it is a scope problem, a capacity problem, or a dependency problem — the remedies are entirely different and applying the wrong one makes it worse.
Then present options with consequences: cut scope (name what), extend (say by how much and what else is affected), or add capacity (which rarely helps late, and often hurts).
Re-baseline once, visibly, rather than slipping a week at a time. Serial small slips destroy credibility far faster than one honest reset.
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 · 57 lines · 68 tokens per session scan A 72e42905a981
program-management is a skill published in the GitHub repository cbrock84/headcount (1,300 stars, last pushed 4d ago), licensed MIT. It adds 68 tokens to every session and 560 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.