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 regulatory-compliancegit 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/regulatory-compliance)<a href="https://agentmods.dev/skills/cbrock84/headcount/regulatory-compliance"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/regulatory-compliance/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/regulatory-compliance"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/regulatory-compliance.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.00071 | $0.00918 |
| Opus 5.5 | $0.00028 | $0.00367 |
| Sonnet 5.5 | $0.00014 | $0.00184 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
regulatory-compliance 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regulatory compliance
Compliance failures are rarely defiance. They are almost always an obligation nobody knew applied, in a jurisdiction nobody was watching, discovered by someone external.
This structures the work and names what to ask. Which regulations apply, and what they require, are legal determinations that vary by jurisdiction and change — they belong with qualified counsel. Nothing here substitutes for that.
Start with an obligation map, not a framework
The first question is not "are we SOC 2 compliant" but "what are we actually obliged to do, by whom, and what happens if we do not." Build the map from facts about the business:
- What you sell, and to whom. Selling to regulated customers pulls their obligations onto you through contract even when the regulation does not reach you directly.
- What data you hold. Personal data, health data, payment data and children's data each carry
distinct regimes — see
legal-risk:privacy-and-data-protection. - Where you operate and where your customers are. Obligations follow the customer more often than companies expect.
- How you are funded and structured. Public, regulated, or government-adjacent adds regimes.
Distinguish three things that get conflated: law you must follow, certifications you choose to obtain commercially, and contractual commitments you signed. Only the first carries state enforcement; all three carry consequences.
Certifications are evidence, not compliance
SOC 2, ISO 27001 and their equivalents demonstrate that controls exist and operate. They do not establish that you meet any legal obligation, and a clean report is not a defense to a regulator.
Where they earn their cost is commercially — an enterprise prospect makes the certification a condition of the deal, and the certification is what unblocks it. Scope them to what the market asks for rather than to everything, since scope drives cost more than any other decision.
The program is monitoring, not documentation
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 d43cc40fbfce
- 1mo ago First seen · 76 lines · 71 tokens per session scan A a9b5dbce25f3
regulatory-compliance is a skill published in the GitHub repository cbrock84/headcount (2,081 stars, last pushed 5d ago), licensed MIT. It adds 71 tokens to every session and 918 once invoked, about $0.0003 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
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.
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.
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.
turbo-pipeline
Use when the user wants a feature built end to end after answering one round of questions and then being left alone — "turbo", "ask me once, then just build it", "I'll answer up front, don't come back to me", "decide the rest yourself". Not for a run that wants a spec approval and no tests (superb:fast-pipeline), one…
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.