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 project-deliverygit 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/project-delivery)<a href="https://agentmods.dev/skills/cbrock84/headcount/project-delivery"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/project-delivery.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.00058 | $0.00965 |
| Opus 5 | $0.00029 | $0.00483 |
| Sonnet 5 | $0.00012 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
project-delivery 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project delivery
A project is one bounded piece of work with an end. Coordinating several toward a shared outcome is
pmo:program-management.
Scope by exclusion
Inclusions are agreed easily and understood differently. The exclusions do the work: what this project will not deliver, written down and acknowledged by the sponsor.
Unwritten exclusions return as assumptions, always late, always framed as something obviously included. Fixing that at the end is called scope creep; it is usually a documentation failure at the start.
Estimate as a range, and say what the range means
A single-point estimate is a forecast presented as a commitment. Give a range with the assumptions that would move it, and be explicit about confidence.
Estimate the work, not the desired date. Estimates negotiated downward do not change the work; they change when you find out, and the finding-out happens at the least recoverable moment.
Decompose until the pieces are comprehensible. Estimating a large unknown produces a number correlated with optimism rather than with the work.
The critical path is where attention belongs
Not everything late matters. Slippage on the critical path moves the end date; slippage elsewhere consumes float. Knowing which is which is the difference between useful concern and generalised anxiety.
Recalculate as things change — the critical path moves, and a team watching the original one is watching the wrong thing.
Hold buffer at the project level rather than padding each task. Padded tasks absorb their own buffer and deliver no earlier, because work expands and nobody reports finishing early.
Track completion, not effort
Percentage complete is self-reported optimism, and it famously stalls at 90%. Track binary completion of defined deliverables — done or not done, judged against a definition agreed in advance.
Watch the trend: whether the amount remaining is falling at the rate required. A project where remaining work is not decreasing is a project that is late, whatever the reported percentage.
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 · 96 lines · 58 tokens per session scan A e9c7e6c11583
project-delivery is a skill published in the GitHub repository cbrock84/headcount (1,300 stars, last pushed 4d ago), licensed MIT. It adds 58 tokens to every session and 965 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.