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 brand-voicegit 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/brand-voice)<a href="https://agentmods.dev/skills/cbrock84/headcount/brand-voice"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/brand-voice.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.00070 | $0.00570 |
| Opus 5 | $0.00035 | $0.00285 |
| Sonnet 5 | $0.00014 | $0.00114 |
| Haiku 4.5 | $0.00007 | $0.00057 |
Grade A, and why
brand-voice 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand voice
The upstream dependency for every writing skill. Draft before this exists and it comes back sounding like everyone else.
With existing samples
Collect ten to twenty real pieces the person considers representative — their best, not their most recent. Then extract, with evidence:
- Sentence rhythm — average length, and whether they vary it deliberately. Most distinctive voices are distinguished by rhythm before vocabulary.
- Vocabulary tells — the words they reach for and the register they avoid. Note both.
- Opening moves — how they start. Most writers have two or three habitual openings.
- Stance — do they assert, hedge, question, or provoke? Who do they assume the reader is?
- Humor and its absence — where it appears and where it never does.
- Formatting habits — paragraph length, list usage, emphasis.
Quote a real example for each. A voice guide with adjectives and no samples is unusable.
Without samples
Build from a choice rather than a blank page. Offer archetypes — the practitioner showing their work, the analyst, the contrarian, the teacher, the insider, the enthusiast — with a written paragraph in each. Let them react. People cannot describe their voice but recognize it instantly.
Then interview around the choice: who are you writing for, what do you want them to feel, what would you never say.
The output
Produce two artifacts other skills read:
voice.md— the rules, each with a real example and a counter-example.about-me.md— background, expertise, recurring themes, and the stories available to draw on.
Include a do-not list. Voice guides fail on what they permit, not what they prescribe.
Verifying
Draft two paragraphs and read them to the person cold. If they say "close, but I wouldn't say it that way," ask exactly what they would say — that correction is the most valuable data in the process.
Never
- Build a voice guide from copy the person did not write. Agency and ghostwritten material describes someone else's voice.
- Describe voice in adjectives alone. "Friendly but authoritative" is unusable without paired examples of what passes and what fails.
- Apply a voice guide to a format it was never sampled from. How someone writes an email is not how they write a keynote.
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 · 55 lines · 70 tokens per session scan A edb3ceb5d0be
brand-voice is a skill published in the GitHub repository cbrock84/headcount (1,300 stars, last pushed 5d ago), licensed MIT. It adds 70 tokens to every session and 570 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
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…