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 endpoint-managementgit 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/endpoint-management)<a href="https://agentmods.dev/skills/cbrock84/headcount/endpoint-management"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/endpoint-management/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/endpoint-management"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/endpoint-management.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.00061 | $0.00792 |
| Opus 5.5 | $0.00024 | $0.00317 |
| Sonnet 5.5 | $0.00012 | $0.00158 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
endpoint-management 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Endpoint management
Endpoints are the most exposed and least controlled part of the estate: they leave the building, run arbitrary software, and are operated by people whose job is not IT.
Enrollment is the control point
A device that never enrolled is a device with no patching, no encryption guarantee, and no remote wipe. Enrollment must be a precondition of access to company data, not a request made afterwards.
Automate it from procurement so a device is enrolled before the user opens it. Manual enrollment as a post-delivery step is skipped exactly when the desk is busy.
Handle personal devices as a deliberate policy decision, not an accident. If personal devices reach company data, either manage the work container or restrict what they can reach — and be explicit with people about what the organization can and cannot see on their own hardware, because ambiguity there destroys trust quickly.
A small number of standard builds
Every additional build variant multiplies testing, support and failure modes. Converge on few, and handle exceptions by adding software to a standard build rather than by creating a new one.
Enforce the security baseline through configuration policy rather than instruction: disk encryption on, screen lock, firewall, up-to-date agents. Anything relying on a user to configure it is configured on some devices.
Patch on a cadence with a deadline
Endpoints patch worse than servers because they are off, asleep, or the user keeps deferring. Allow deferral with a hard deadline and force after it, and communicate the deadline in advance — an unexpected forced reboot during a customer call is what teaches people to avoid management.
Report coverage as a percentage of the fleet, and specifically chase the long tail. The devices that never appear in patch reports are usually the interesting ones: traveling users, spares, and the machine in a cupboard still holding a domain account.
Lost, stolen, or leaving
Have the sequence ready in advance: lock, locate if possible, wipe, revoke credentials and sessions,
and record what data was on it for legal-risk:privacy-and-data-protection to assess notification.
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 3cecf0f015d7
- 1mo ago First seen · 72 lines · 61 tokens per session scan A a7b24c529981
endpoint-management is a skill published in the GitHub repository cbrock84/headcount (2,075 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 792 once invoked, about $0.0002 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
embedded-systems-architect
Embedded systems and Edge AI architecture assistant for development-board projects. Use when the user works with dev boards, SoC, MCU or microcontroller (datasheet, TRM, HDK, schematics), firmware or RTOS development, cross-compilation, SDK / BSP / sample code, board families such as Jetson, Raspberry Pi, ESP32…
addin-operations
TIA Portal Add-In development in Visual Studio Code: creating Add-In C# projects, adding Add-In templates, compiling and debugging Add-Ins, converting Add-Ins from older TIA Portal versions and configuring Add-In project parameters.
tia-doctor
Manual, read-only prerequisite probe for TIA Portal V21 and its modular Openness API, with an optional Python TIA Scripting check.
tia-import-export
C# Openness implementation of import/export and round-trip engineering.
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.