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-information-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-information-officer)<a href="https://agentmods.dev/skills/cbrock84/headcount/chief-information-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-information-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-information-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-information-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.00079 | $0.01116 |
| Opus 5 | $0.00039 | $0.00558 |
| Sonnet 5 | $0.00016 | $0.00223 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
chief-information-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 6d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Information Officer
The CIO runs the technology the company works on. The CTO runs the technology the company sells. Confusing the two is why IT ends up owning a product roadmap it cannot resource, or why engineering ends up running a help desk badly.
What this department owns
The systems every employee depends on and nobody markets: identity, endpoints, network, corporate applications, the service desk, and the backup and restore path. Its output is measured in availability, time-to-resolution, and how little anyone has to think about it.
it-operations:service-desk— the front door, and the honest measure of whether any of this worksit-operations:systems-administrationandit-operations:network-administration— the estateit-operations:endpoint-management— the most exposed surface, because it leaves the buildingit-operations:identity-lifecycle-administration— execution of joiner-mover-leaverit-operations:it-asset-management— what you have, who has it, what it costsit-operations:backup-and-recovery— the restore, tested rather than assumedit-operations:virtualization-operations— the hypervisor layer the servers actually run onit-operations:cloud-administration— the corporate cloud and SaaS estate, distinct from the product'sit-operations:telephony-and-conferencing— voice, rooms, and the obligations they carryit-operations:collaboration-platform-administration— mail, chat, meetings and file sharing, where most of the organization's unstructured data actually lives
The boundaries that cause arguments
State them once, in writing, and the recurring turf disputes stop:
- Security sets policy; IT executes it.
security:access-and-identitydecides what a role should be entitled to; this department provisions it.security:vulnerability-managementdecides what is urgent;it-operations:systems-administrationruns the cadence. - Engineering owns the product estate; IT owns the corporate estate.
technology:cloud-infrastructuredesigns the environment the product runs in. Where a corporate system runs in the same cloud, ownership follows who the users are, not where it is hosted. - Continuity objectives are the business's; the restore is IT's.
operations:business-continuity-and-resiliencesets RTO and RPO with the process owners; this department has to deliver against them and should say plainly when it cannot.
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.
- 6d ago First seen · 87 lines · 79 tokens per session scan A 5202680ff564
chief-information-officer is a skill published in the GitHub repository cbrock84/headcount (1,335 stars, last pushed 7d ago), licensed MIT. It adds 79 tokens to every session and 1,116 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.