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 self-service-and-knowledgegit 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/self-service-and-knowledge)<a href="https://agentmods.dev/skills/cbrock84/headcount/self-service-and-knowledge"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/self-service-and-knowledge.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.00075 | $0.00714 |
| Opus 5 | $0.00037 | $0.00357 |
| Sonnet 5 | $0.00015 | $0.00143 |
| Haiku 4.5 | $0.00007 | $0.00071 |
Grade A, and why
self-service-and-knowledge 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-service and knowledge
Good self-service is the cheapest support you will ever run and the most neglected. It is also frequently the wrong answer — an article explaining a confusing screen is a bandage on a design problem.
Decide what deserves an article
Before writing, ask whether the contact should exist. If people repeatedly need instructions for one screen, the screen is the defect. Documenting it makes the problem permanent and invisible.
Write articles for things that are genuinely complex, genuinely occasional, or genuinely outside your control. Not for things that are merely badly designed.
What to write, and in what order
Rank by contact volume, not by feature importance. The most-viewed help content is almost never what the team expected — it is billing, access, and the one confusing setting.
Structure each article around the customer's task, in their words, not your feature's name. People search for what they are trying to do.
- Answer first. The steps in the first screen, context afterward. Nobody arrives wanting background.
- One task per article. Combined articles fail search, because the match lands on the wrong half.
- Show the actual interface — real labels, real button names, updated when they change.
- Say what to do when it does not work. The next step, and how to reach a human. Making that hard converts a solvable problem into a complaint about you hiding.
Findability decides everything
An article nobody finds does not exist. Findability comes from titles matching real search language, in-product links at the moment of confusion, and search that tolerates the words customers actually use rather than your internal vocabulary.
Read your help-center search logs, especially the queries returning nothing. That list is your content backlog, ranked by demand, already written for you.
In-product beats the help center
Guidance at the point of confusion deflects far more than a help center does, because it requires no decision to go looking. A well-written empty state, field hint, or error message removes contacts that documentation never would.
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 Changed · +7 lines e823a6d2607e
- 9d ago First seen · 65 lines · 75 tokens per session scan A 6ec06c25248b
self-service-and-knowledge is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 5d ago), licensed MIT. It adds 75 tokens to every session and 714 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-08-30.
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.
dns
This skill should be used when the user asks about "DNS", "domain resolution", "GeoDNS / geo routing", "latency-based routing", "weighted / failover routing", "Route 53 / Cloud DNS", an "A/CNAME/ALIAS record", "anycast", or "DNS TTL / propagation". It gives the global front door that maps a name to the right IP and…