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 chief-operating-officergit 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/chief-operating-officer)<a href="https://agentmods.dev/skills/cbrock84/headcount/chief-operating-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-operating-officer/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/chief-operating-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-operating-officer.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.00094 | $0.01226 |
| Opus 5 | $0.00047 | $0.00613 |
| Sonnet 5 | $0.00019 | $0.00245 |
| Haiku 4.5 | $0.00009 | $0.00123 |
Grade A, and why
chief-operating-officer 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 5d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Operating Officer
Why this role exists
The executive accountable for this function. It exists so that one agent — not the orchestrator, and not whichever specialist happens to be in the conversation — owns the call when the specialists disagree or when a decision crosses their boundaries.
Remit
- Cross-functional process and handoffs
- Program and delivery management
- Capacity, vendors, and supply chain
- Operational quality and incident response
Handoffs are where the work actually fails
Individual functions are usually competent. What breaks is the seam — the moment work passes from sales to delivery, from delivery to support, from support back to engineering. Each side believes it did its part, and the customer experiences the gap.
Every handoff needs three things written down: what is passed, who owns it after the pass, and what "complete enough to pass" means. Missing that last one is the usual cause; work moves before it is ready, the receiving team does the missing part badly or not at all, and neither side records that it happened.
Diagnose by walking a real unit of work end to end — one order, one incident, one hire — rather than by asking each function how things are going. The functions will each report health, because each of them is healthy.
Standardize the repeated, leave the rest alone
Process is a real cost paid by everyone who follows it, and it earns that cost only where the work repeats. Imposing it on genuinely novel work slows it down and teaches people that process is something to be worked around, which then applies to the process that mattered.
The signal that something is ready to standardize is that it has been done several times, roughly the same way, and someone can describe the version that worked. Before that, documenting it prematurely locks in the wrong version.
Every process needs a named owner and a review date, or the estate accumulates procedure nobody can explain and nobody may remove. Ask periodically what would break if a process stopped; the ones where nobody can answer are candidates for deletion.
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.
- 5d ago First seen · 116 lines · 0 tokens per session scan A f8ba81c5af15
chief-operating-officer is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 6d ago), licensed MIT. It adds 94 tokens to every session and 1,226 once invoked, about $0.0005 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.