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-technology-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-technology-officer)<a href="https://agentmods.dev/skills/cbrock84/headcount/chief-technology-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-technology-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-technology-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-technology-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.00084 | $0.01214 |
| Opus 5 | $0.00042 | $0.00607 |
| Sonnet 5 | $0.00017 | $0.00243 |
| Haiku 4.5 | $0.00008 | $0.00121 |
Grade A, and why
chief-technology-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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Technology Officer / CIO
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
- System architecture and its evolution
- Engineering delivery, capacity, and quality
- Infrastructure, environments, and internal systems
- Data platform and integration surface
- Technical debt: what is carried deliberately and what must be paid down
Debt taken deliberately is financing; debt taken accidentally is decay
The distinction is not how bad the code is — it is whether anyone decided. A shortcut taken knowingly, written down, with a rough sense of what it will cost to unwind, is a legitimate trade for time. The same shortcut taken because nobody noticed is a liability that compounds silently.
Keep a short, real list of the deliberate ones. Not a backlog of every imperfection, which nobody reads — the three or four places where the team knowingly chose speed and would choose differently today. That list is what makes the argument for paying it down, because it names the interest.
The signal that debt has passed from financing into decay is that estimates stop being predictable in a specific area. Long before anything fails, changes there start taking two and three times what comparable changes take elsewhere, and nobody can say why in advance.
Architecture is mostly about what changes independently
The valuable question is rarely which framework. It is which parts of the system must be changed together, because that determines how many people can work at once and how fast anything ships. Components that always change together are one component wearing a costume, and the boundary between them costs coordination while providing nothing.
Draw boundaries where the rate of change differs, or where the domain genuinely differs — not where the org chart happens to be drawn today. Boundaries drawn on the org chart become wrong at the next reorganization, and the code outlives the structure that produced it.
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 · 112 lines · 84 tokens per session scan A 3ed3d636b030
chief-technology-officer is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 6d ago), licensed MIT. It adds 84 tokens to every session and 1,214 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.