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 disputes-and-legal-holdsgit 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/disputes-and-legal-holds)<a href="https://agentmods.dev/skills/cbrock84/headcount/disputes-and-legal-holds"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/disputes-and-legal-holds/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/disputes-and-legal-holds"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/disputes-and-legal-holds.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.00095 | $0.00823 |
| Opus 5 | $0.00048 | $0.00411 |
| Sonnet 5 | $0.00019 | $0.00165 |
| Haiku 4.5 | $0.00010 | $0.00082 |
Grade A, and why
disputes-and-legal-holds 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 8d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Disputes and legal holds
The decisions that determine how a dispute goes are made in the first week, usually by people who do not know a dispute has started.
This structures the operational response. Procedural obligations and their deadlines vary by jurisdiction and forum — get counsel engaged early, and let them drive strategy.
Preservation attaches earlier than most people expect
The obligation to preserve begins when litigation is reasonably anticipated — which can be a demand letter, a threat made in a meeting, a regulator's inquiry, or an internal complaint serious enough that a claim is foreseeable. It does not wait for a filing.
Destruction after that point is treated far more seriously than the underlying dispute. Routine automatic deletion continuing through a hold is the common version, and "it was our normal policy" is not the defense people assume.
Issue the hold in writing, and make it reach the systems
A hold has two halves and organizations routinely do only the first.
- Notify the people. Written, naming the matter in general terms, describing the categories of material to preserve, instructing recipients not to delete and not to discuss, and requiring acknowledgment. Identify custodians by what they touched, not by seniority.
- Suspend the machinery. Automatic deletion runs on schedules nobody remembers setting: mail retention, chat history expiry, ticket archival, log rotation, backup rotation, CRM purges, device wipe on offboarding. Each needs an explicit suspension for the affected scope.
The systems half is where holds fail, because the notice goes out and everyone assumes it was sufficient. Keep a list of every system with an automatic deletion schedule so that the question is answerable in an afternoon rather than a fortnight.
Maintain the hold as a live thing
Re-notify periodically, add custodians as the matter develops, and cover departures — an employee leaving under a hold means their mailbox, files and device do not follow the standard offboarding path. Release the hold in writing when counsel says so, and only then.
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.
- 8d ago First seen · 77 lines · 95 tokens per session scan A 404eb222b961
disputes-and-legal-holds is a skill published in the GitHub repository cbrock84/headcount (1,356 stars, last pushed 9d ago), licensed MIT. It adds 95 tokens to every session and 823 once invoked, about $0.0005 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.
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.
go
Compatibility entry for Visual Stack's former /vstack:go command. Runs the wireframe and UI review tool, now called review. Use only when the user invokes /vstack:go.