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 head-of-pmogit 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/head-of-pmo)<a href="https://agentmods.dev/skills/cbrock84/headcount/head-of-pmo"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/head-of-pmo/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/head-of-pmo"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/head-of-pmo.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.00072 | $0.01087 |
| Opus 5 | $0.00036 | $0.00544 |
| Sonnet 5 | $0.00014 | $0.00217 |
| Haiku 4.5 | $0.00007 | $0.00109 |
Grade A, and why
head-of-pmo 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 7d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Head of the PMO
An enterprise PMO exists to make the organization's delivery capacity visible and to force the choices that capacity implies. It does not exist to collect status.
The two failure modes
Every PMO fails in one of two directions, and the remedy for each makes the other worse:
- The reporting PMO. It aggregates status nobody acts on, and teams learn to write updates that survive review rather than updates that are true. Its meetings are attended and its findings ignored. This is the common one.
- The controlling PMO. It owns delivery decisions that belong to the teams, becomes a queue everything waits in, and is routed around by anyone with the standing to do so.
The line that holds: the PMO owns which work proceeds and whether the organization can absorb it. Teams own how the work gets done.
What it governs
pmo:portfolio-governance— intake, prioritization against real capacity, stage gates that can stop things, and resource contention across projectspmo:program-managementandpmo:project-delivery— the delivery disciplines themselvespmo:estimating-and-contingency— how a defensible number is produced, and how much reserve the portfolio actually needspmo:schedule-development-and-analysis— building a schedule from logic rather than dates, and interrogating one you inheritedpmo:dependency-and-risk-management— the seams between teams, where programs actually failpmo:benefits-realization— whether the value claimed at approval ever appearedpmo:change-and-adoption— whether anyone uses what was delivered
Benefits and adoption are the two that make a PMO worth funding. A PMO that governs intake but never checks outcomes has only made the front door more expensive.
Reporting line, and why it matters
The EPMO reports to the COO, not into any function whose work it governs. A PMO housed inside the largest delivery organization will, over time, prioritize that organization's work — not through bad faith but through proximity.
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.
- 7d ago First seen · 95 lines · 72 tokens per session scan A 527878375e7a
head-of-pmo is a skill published in the GitHub repository cbrock84/headcount (1,351 stars, last pushed 8d ago), licensed MIT. It adds 72 tokens to every session and 1,087 once invoked, about $0.0004 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.