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 it-asset-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/it-asset-management)<a href="https://agentmods.dev/skills/cbrock84/headcount/it-asset-management"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/it-asset-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/it-asset-management"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/it-asset-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.00054 | $0.00722 |
| Opus 5 | $0.00027 | $0.00361 |
| Sonnet 5 | $0.00011 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
it-asset-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 5d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IT asset management
The register exists to answer operational questions: what do we have, who has it, is it supported, is it licensed, and when does it need replacing. An inventory that answers none of those is an accounting artifact.
One register, reconciled against reality
A register maintained by hand diverges immediately. Feed it from discovery — what is actually on the network and enrolled in management — and reconcile against procurement and finance records.
The valuable output is the discrepancy list: assets in the register that discovery cannot find, and devices discovery finds that the register does not know about. The second category is the security problem, since an unknown device is unmanaged by definition.
Ownership, not just location
Every asset needs a named accountable person. "The engineering team" is not an owner; when the device needs patching, returning or replacing, a team does not answer.
Track state through the lifecycle — ordered, in stock, assigned, in repair, retired, disposed — and require the state change at the moment of handover. A register updated in batches is a register that is wrong between batches, which is most of the time.
Software licensing
Under-licensing is a financial and legal exposure that surfaces at audit; over-licensing is money spent on nothing, and it is usually the larger number.
Reconcile entitlements against actual installs and actual use. Reclaiming licenses from people who stopped using a tool typically funds a meaningful fraction of the next renewal, and the data for it already exists.
Watch license models that change cost with infrastructure — per-core, per-socket, per-user in a system that provisions freely. A routine infrastructure change can multiply a license bill with no procurement decision anywhere in the path.
Refresh and disposal
Plan refresh on a cycle and budget it as a steady cost through
finance:budgeting-and-forecasting. Refresh driven by failure produces an unpredictable expense and
a worse experience, and it always arrives at the wrong moment.
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.
- 5d ago First seen · 73 lines · 54 tokens per session scan A 7aa106b24b57
it-asset-management is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 722 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
user-story-map
Build an interactive, drag-and-drop user story map so the user can re-slice work across release phases. Use when the user wants a story map, a phased roadmap, release slicing, a backbone/activities journey map, or to decide "which stories go in which phase" and move them around.
agile-ledger
Plain-Markdown Scrum / Agile product-management system for Claude Code. Manage a product backlog of Epics and User Stories, plan and run sprints, drive a board, track velocity, cut Major.Minor releases, and keep GitHub branches/commits/PRs traceable to stories — all from slash commands, with no Jira and no database.…
agile-ledger-workspace
Optional multi-repo orchestrator for Agile-Ledger. Install once at a workspace root to manage many repositories at once: discover new repositories on a GitHub org (including ones nobody told you about), clone and bootstrap them, run a single cross-repo "what changed while I was away" sync, and reconstruct undocumented…
people-integration
Design the first 90 days for acquired product talent so they stay, contribute, and feel ownership. Produces decision map session template, mentor pairing matrix, 30/60/90 ownership plan, retention risk review (purpose and influence), and 1:1 coaching question library.
roadmap-convergence
Facilitate the post-acquisition roadmap convergence process across Weeks 1 to 8. Produces the conflict log, three-session facilitation guides, merged 90-day plus 12-month roadmap, and the 30/60/90 execution plan.
week-0-readiness
Run a product leader through pre-close (Week 0) integration readiness for an acquisition. Produces the integration lead charter, decision rights one-pager, combined product narrative draft, customer commitment inventory, and the five-question Day 1 readiness check.