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 service-deskgit 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/service-desk)<a href="https://agentmods.dev/skills/cbrock84/headcount/service-desk"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/service-desk.svg" alt="Measured on agentmods" 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.00073 | $0.01100 |
| Opus 5 | $0.00036 | $0.00550 |
| Sonnet 5 | $0.00015 | $0.00220 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
service-desk 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 4d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service desk
The service desk is where the whole IT organization is judged, usually by people having a bad day. Most of what makes it good is intake discipline and honest measurement.
Intake determines everything downstream
Capture enough at first contact to route correctly and act without a second exchange: who, what they were doing, what happened, what they expected, and how blocked they are.
Give the requester a single channel that works. Multiple half-supported channels — a queue, a chat, a shoulder tap, a manager's direct message — mean the loudest request wins rather than the most urgent, and the desk's workload becomes unmeasurable because most of it is invisible.
Priority is impact against urgency
Priority is not a feeling. Define it on two axes — how many people are affected and how blocked they are — and publish the matrix so it can be applied consistently rather than argued each time.
Keep incidents (something broken) separate from requests (something wanted). They have different clocks, different queues, and different success conditions, and merging them lets routine requests bury outages.
Escalation should be time-based and automatic. Relying on someone to notice a ticket aging means the tickets that age are the ones nobody is watching.
Measure service, not activity
Tickets closed measures activity, and optimizing it produces premature closure and reopened tickets. Better:
- First-contact resolution — resolved without a handoff.
- Time to resolution at the percentile users feel, not the mean.
- Reopen rate — the direct check on premature closure.
- Repeat contacts for the same underlying cause — the number that points at problems worth eliminating.
Never target an individual on volume. It reliably produces cherry-picking of easy tickets and quiet avoidance of hard ones.
Eliminate demand rather than absorbing it
A desk that handles the same failure two hundred times has done two hundred units of work and solved nothing. Cluster tickets by underlying cause and feed the top few into permanent fixes — a configuration change, a fix at source, or self-service that genuinely resolves.
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.
- 4d ago First seen · 102 lines · 73 tokens per session scan A e5d9aa9e5e6e
service-desk is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 5d ago), licensed MIT. It adds 73 tokens to every session and 1,100 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
manage-glue-workers
Use when managing engineers who naturally gravitate toward glue work (onboarding, documentation, unblocking, process improvement) and need protection from burnout, visibility for their impact, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how…
commitments
Use to track what the user has promised — to their manager, execs, partner teams — and to keep those promises from silently going stale. Trigger phrases include "what have I committed to", "add a commitment", "I promised X by Friday", "am I overcommitted", "help me say no to this", "I need to renegotiate a deadline".…
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.
structure-swift-sources
Organize Swift source trees and oversized Swift files by feature, layer, and declaration group; split large files, normalize // MARK: sections, enforce plain-language block-comment file headers, and move TODO and FIXME text into ledger files. Use after format-swift-sources has established a clean formatting baseline.
tips-helpviewer-workflow
Discover local user-guide topics for installed Apple Mac apps through the Tips HelpViewer catalog, with app matching, installed-version capture, result verification, and authoritative fallback routing. Use when Codex needs task-specific help for an installed Apple app, needs to find a menu command through local Help…
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.…