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-human-resources-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-human-resources-officer)<a href="https://agentmods.dev/skills/cbrock84/headcount/chief-human-resources-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-human-resources-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-human-resources-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-human-resources-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.00090 | $0.01252 |
| Opus 5 | $0.00045 | $0.00626 |
| Sonnet 5 | $0.00018 | $0.00250 |
| Haiku 4.5 | $0.00009 | $0.00125 |
Grade A, and why
chief-human-resources-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 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Human Resources 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
- Org design and reporting structure
- Hiring, leveling, and compensation bands
- Performance management and development
- Culture, engagement, and employee relations
What separates this role from running HR is the governance half
Below a certain scale, this job is hiring, compensation, and employee relations. Above it — and immediately, in any company with a board, institutional investors, or a path to being public — a second half appears that is closer to finance and legal than to people operations.
That half includes executive compensation designed with the board's compensation committee rather than proposed to it, succession planning for roles the board cares about, disclosure obligations where compensation and workforce data become public documents, and internal controls over HR processes that get tested like financial ones. Payroll, benefits administration, and equity recordkeeping all carry control requirements, and the failures are audit findings rather than morale problems.
Workforce data is increasingly reported externally as well. Once a number is disclosed, its definition is frozen — which makes the definition a decision worth making carefully the first time, because restating it later invites the question of what changed.
Executive compensation is where this role is most exposed and least able to delegate. It is simultaneously a retention instrument, a governance artifact, and a public signal, and the three pull in different directions.
Org design decides more than any individual hire
Structure determines what is easy: who talks to whom without a meeting, which tradeoffs get made by one person, and which require a committee. A reorganization is usually an attempt to fix a coordination problem, and it works only where the problem was genuinely structural rather than a disagreement two people were avoiding.
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 · 122 lines · 0 tokens per session scan A 91d54c783fb2
chief-human-resources-officer is a skill published in the GitHub repository cbrock84/headcount (1,351 stars, last pushed 7d ago), licensed MIT. It adds 90 tokens to every session and 1,252 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
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
mode
Show or set NeatContext routing to auto, ask, or manual for Codex, with an optional default shared with every other NeatContext host. Use only when the user explicitly invokes this skill or clearly asks to change routing behavior.
status
Report the NeatContext context and routing mode active in Codex, including missing-file or stale-routing warnings. Use when the user asks which context is connected or explicitly invokes this skill.
list
List the local NeatContext Contexts available to Codex. Use when the user asks what contexts exist, what can be connected, or explicitly invokes this skill.
hermes-agent-compatibility
Audit Socket-to-Hermes compatibility across Agent Skills, Codex plugins, MCP, hooks, apps, agents, and Hermes extension systems. Use for skill exports, config translations, and Hermes adapter decisions.
build-oxpecker-web-app
Build or modify an Oxpecker web application in idiomatic F#, using endpoint routing, functional EndpointHandler and EndpointMiddleware composition, ASP.NET Core metadata, and focused endpoint tests.