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 employment-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/employment-compliance)<a href="https://agentmods.dev/skills/cbrock84/headcount/employment-compliance"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/employment-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/employment-compliance"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/employment-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.00087 | $0.00834 |
| Opus 5 | $0.00044 | $0.00417 |
| Sonnet 5 | $0.00017 | $0.00167 |
| Haiku 4.5 | $0.00009 | $0.00083 |
Grade A, and why
employment-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 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Employment compliance
This is the area where a well-intentioned decision made quickly costs the most later, because the mistakes are cheap to make, invisible for years, and expensive per-employee once found.
This structures the questions and the common failure patterns. Employment law varies by country, state and locality, changes often, and turns on specific facts — get a qualified employment adviser before acting on a classification, a termination, or a policy that applies to everyone.
Classification is decided by the work, not by the title or the agreement
Exempt versus non-exempt determines whether someone is owed overtime. It turns on what the person actually does day to day and on a salary threshold, not on being salaried, having a senior title, or preferring it that way. A misclassified role accrues unpaid overtime quietly and for everyone in it.
Employee versus contractor turns on control and independence — who decides how, when and where the work is done, who supplies the tools, whether the person serves other clients, and how integrated the work is with the business. A signed contractor agreement does not settle it. The common pattern that fails is a long-term contractor who works your hours, on your equipment, under your direction, on core work.
Reclassify when the facts change. A contractor who has become a de facto employee does not stay a contractor because nobody revisited it.
Hours, breaks and the records that prove them
Non-exempt time has to be recorded, including work done outside scheduled hours. Answering messages after hours is time worked, and an organization that expects it while not recording it has created an unpaid-hours exposure with an audit trail in its own chat logs.
Rules on breaks, rest periods, split shifts, on-call time and travel time vary sharply by jurisdiction and are the ones most often missed by a policy written for headquarters and applied everywhere.
Work authorization and personnel records
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 · 75 lines · 87 tokens per session scan A 67795b7c4c85
employment-compliance is a skill published in the GitHub repository cbrock84/headcount (1,351 stars, last pushed 8d ago), licensed MIT. It adds 87 tokens to every session and 834 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.