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 agentmods add skills/cbrock84/headcount/employee-relationsnpx skills add cbrock84/headcount --skill employee-relationsgit 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/employee-relations)<a href="https://agentmods.dev/skills/cbrock84/headcount/employee-relations"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/employee-relations.svg" alt="Measured on agentmods" height="20"></a>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.00065 | $0.00635 |
| Opus 5 | $0.00032 | $0.00318 |
| Sonnet 5 | $0.00013 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
employee-relations 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 2d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Employee relations
These situations are consequential for the person, for the organization's legal exposure, and for everyone watching how it is handled. Process is what protects all three.
This structures the approach and tells you what to ask. Grievances, investigations, dismissals, discrimination and accommodation are legally regulated and vary substantially by jurisdiction — involve qualified employment counsel early rather than at the point of decision.
Take complaints seriously and visibly
How the first complaint is handled determines whether you hear about the second. An organization that mishandles one complaint does not stop having problems; it stops being told about them, and then learns about them from a regulator or a lawyer.
Acknowledge promptly, explain what will happen next, and say what the person can expect to be told. Do not promise confidentiality you cannot deliver — say who will need to know and why. A broken confidentiality promise destroys the reporting channel permanently.
Protect against retaliation actively. Retaliation is frequently a worse exposure than the original complaint, and it often occurs through ordinary decisions — a changed assignment, an excluded invitation — made by someone who would deny any such intent.
Investigations
An investigation establishes what happened. It is not a negotiation and not a disciplinary process.
- Independent investigator — not in the reporting line of anyone involved.
- Scope agreed in writing at the start, so it neither drifts nor is later described as narrow.
- Both sides heard, with the respondent told the substance of the allegation in enough detail to answer it.
- Contemporaneous notes, and evidence preserved from the moment you are aware.
- Findings on the balance of evidence, stated separately from any recommendation.
Move quickly. Investigations that drift damage everyone involved and the delay itself becomes a complaint.
Conflict that is not misconduct
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.
- 2d ago First seen · 66 lines · 65 tokens per session scan A 1f5544854bf7
employee-relations is a skill published in the GitHub repository cbrock84/headcount (1,284 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 635 once invoked, about $0.0003 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.