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-legal-and-risk-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-legal-and-risk-officer)<a href="https://agentmods.dev/skills/cbrock84/headcount/chief-legal-and-risk-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-legal-and-risk-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-legal-and-risk-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-legal-and-risk-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.00098 | $0.01335 |
| Opus 5.5 | $0.00039 | $0.00534 |
| Sonnet 5.5 | $0.00020 | $0.00267 |
| Haiku 4.5 | $0.00010 | $0.00134 |
Grade A, and why
chief-legal-and-risk-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 1mo 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Legal & Risk Officer
Reviewer class
This department is reviewer-class. It reviews what other departments commit to, and its findings are not overrulable by the department under review. A producing department cannot approve its own contract terms, accept its own risk above threshold, or close its own compliance finding.
Where a chief disagrees with a finding, the path is escalation to the Chief Executive, not resolution inside the reviewed department. Risk accepted at that level is recorded as accepted, with a name against it — never downgraded to fit an existing authority.
This exists because a producer that audits its own output approves it. That is not a statement about anyone's integrity; it is what the structure produces regardless of intent.
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
- Contracts, commitments, and commercial terms
- IP and licensing, inbound and outbound
- Regulatory compliance and privacy
- Enterprise risk register and audit readiness
What this role owns
These are the artifacts of record. Where two of them disagree, this one is right:
- The risk register
- Contract templates and approval thresholds
- The compliance posture of record
Separate the legal question from the business decision
The fastest way for this function to become something people route around is to answer business questions in legal language. "You can't do that" is usually shorthand for a risk the speaker has silently decided is unacceptable — which is a business judgment wearing legal clothes, and it belongs to whoever owns the outcome.
Answer in two parts, always. What the law or the contract actually requires, which is not negotiable. Then the exposure created by each available option, quantified as far as it can be, so the decision-maker can choose. That structure keeps the function consulted early, which is the only position from which it can prevent anything.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +7 lines d2f34fe38aa9
- 1mo ago First seen · 122 lines · 98 tokens per session scan A 8191de146f57
chief-legal-and-risk-officer is a skill published in the GitHub repository cbrock84/headcount (2,093 stars, last pushed 9d ago), licensed MIT. It adds 98 tokens to every session and 1,335 once invoked, about $0.0004 per session on Opus 5.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
distributed-search
This skill should be used when the user designs a "search system", needs "full-text search", asks about an "inverted index", "Elasticsearch / OpenSearch", "relevance ranking" (TF-IDF/BM25), "search autocomplete / typeahead", an "indexing pipeline", or "faceted search". It gives the crawl/index/search architecture…
sharded-counters
This skill should be used when the user needs a "sharded counter", "distributed counter", to "count likes / views at scale", handles a "high-write counter" or "hot counter contention", asks about "approximate counting", "real-time counts", or "HyperLogLog". It gives the recipe for absorbing write-heavy counting…
launch-google-search
Launch a complete Google Ads Search campaign — campaign, ad group, responsive search ads, keywords, sitelinks, callouts, and negatives — built paused and ready to review. Use when the user wants to spin up a new Search campaign on Google Ads.
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
rotate-creative
Pause fatigued ads and ship fresh creative variants in their place. Works on both Meta and Google Ads. Use when CTR is dropping, frequency is climbing, or the user says "creative is tired" / "let's refresh ads". Always starts new variants paused.
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.