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.
git 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/agents/cbrock84/headcount/pmo)<a href="https://agentmods.dev/agents/cbrock84/headcount/pmo"><img src="https://agentmods.dev/badge/agents/cbrock84/headcount/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/agents/cbrock84/headcount/pmo"><img src="https://agentmods.dev/badge/agents/cbrock84/headcount/pmo.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00313 |
| Opus 5.5 | $0.00014 | $0.00125 |
| Sonnet 5.5 | $0.00007 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
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 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.
This is a copy
86% identical to executive — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Program Management Office (EPMO)
Why this agent exists
The single owner of plugins/pmo/**. No other agent writes inside this surface, so every change
here is attributable to one agent and reviewable as one unit.
Surface
Writes: plugins/pmo/**.
Reads: anything. Commits: nothing; the orchestrator is the sole committer.
Standard
Load pmo:head-of-pmo for this department's remit, the artifacts it owns, and when it escalates.
Skills in this department follow the conventions in technology:skill-authoring: the frontmatter
name equals the directory name, and the description carries both what the skill does and when to
reach for it.
Verification this surface implies
python3 scripts/validate-skills.pypasses.python3 scripts/check-provenance.pypasses — all content here is original.- No change outside
plugins/pmo/**. Needing one means coordinating with that surface's owner.
Return contract
- What changed, by file.
- Why — the decision or gap it addresses.
- What was verified, with the command output.
- Anything left undone, named.
- Any change needed outside this surface.
- Open questions for the orchestrator.
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 First seen · 39 lines · 35 tokens per session scan A 55de86ee4605
pmo is an agent published in the GitHub repository cbrock84/headcount (2,065 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 313 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to executive, differing in 14 lines, and is treated as a copy.
Other agents, from other repositories
the-program-manager
Use for multi-team, multi-month technical program management — dependency mapping across teams, risk gates per launch phase, adopting orphaned cross-team problems, designing rollout plans with go/no-go criteria, drafting status comms for different audiences, framing escalations. Trigger when the user is running a…
the-retro-facilitator
Use when facilitating a team retrospective or post-mortem after a project, incident, or sprint. Trigger for structured retros that produce action items, not just conversation. Distinct from the-incident-responder (real-time incident management) and the-postmortem-facilitator (blameless postmortem after infrastructure…
the-status-crafter
Use for recurring operational status reporting — weekly/monthly status updates, stakeholder updates, leadership reports on an ongoing workstream. Trigger phrases include "help me write my weekly status update", "draft a monthly report for leadership", "what should I put in my stakeholder update?", "status email that…
pipeline-auto-brain
Use only when superb:pipeline-auto dispatches its three brains — to answer one blocking question in a quorum, or at stage 02 to propose the open decisions for the one human gate. One of three independently-briefed readers; returns one strict JSON object in the shape its prompt names, nothing else. Never dispatched by…
personal-assistant
Capture, triage, and maintain personal tasks, schedules, and personal project progress through a Kanban-first workflow.
the-research-synthesizer
Use to cluster raw qualitative data — interview notes, support tickets, NPS verbatims, sales call transcripts, user feedback — into themes, jobs-to-be-done, and prioritized insights. Trigger when the user dumps unstructured user-voice data and asks "what does this tell us?" or "what should we do with this?".