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 corporate-governancegit 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/corporate-governance)<a href="https://agentmods.dev/skills/cbrock84/headcount/corporate-governance"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/corporate-governance/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/corporate-governance"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/corporate-governance.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.00088 | $0.00753 |
| Opus 5 | $0.00044 | $0.00377 |
| Sonnet 5 | $0.00018 | $0.00151 |
| Haiku 4.5 | $0.00009 | $0.00075 |
Grade A, and why
corporate-governance 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corporate governance
The record of what the company decided, who was allowed to decide it, and what happens when something goes wrong. Unglamorous until it is the only thing that matters.
The corporate record
One authoritative place holding: formation and entity documents, ownership and cap table, board and shareholder resolutions, minutes, signed agreements above the review threshold, insurance policies, and material licenses and registrations.
The failure mode is not losing a document; it is not knowing which version is current. Every record carries its effective date, and superseded versions are marked superseded rather than deleted — "what was in force in March" is a question that gets asked in exactly the circumstances where you cannot afford to guess.
Board and committee support
Materials go out with enough notice to actually be read — a deck delivered the night before produces a meeting where the deck is presented rather than discussed.
Each item is labeled by what it needs: decide, discuss, or note. Meetings run long because everything is presented as if it needs all three.
Minutes record decisions, who was present, who abstained or recused, and the basis on which a decision was taken. They are not a transcript. Where a decision was contested, that is worth recording — it is evidence the board exercised judgment rather than rubber-stamping.
Delegations of authority
Write down who can commit the company to what, at which value, and what requires escalation. Cover spending, contracts, hiring, and anything creating a long-term obligation.
Two failures, both common: thresholds so low that everything escalates and the process is routed around, and thresholds nobody wrote down, so authority is whatever was not challenged last time.
Review after any material change in size or structure.
Insurance and continuity
Know what is covered, what is excluded, what the limits are, and who to call. The exclusions matter more than the coverage and are read least.
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 · 73 lines · 88 tokens per session scan A ab1f1850b670
corporate-governance is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 6d ago), licensed MIT. It adds 88 tokens to every session and 753 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
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.