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.
git 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/agents/cbrock84/headcount/verticals)<a href="https://agentmods.dev/agents/cbrock84/headcount/verticals"><img src="https://agentmods.dev/badge/agents/cbrock84/headcount/verticals/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/agents/cbrock84/headcount/verticals"><img src="https://agentmods.dev/badge/agents/cbrock84/headcount/verticals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00576 |
| Opus 5.5 | $0.00000 | $0.00230 |
| Sonnet 5.5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
verticals 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 29d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vertical packs
Why this agent exists
The single owner of verticals/**. Each vertical is a config plus the content that makes the core
specific to one industry, and scripts/build-vertical.py emits a standalone repository from the
two. No other agent writes inside this surface.
It is separate from the departments because the content crosses them — an industrial vertical adds
to operations, people and legal-risk at once — and separate from repo-meta because writing
industry advice is not the same job as maintaining the generator that ships it.
Authority: proposes
Diffs here are surfaced before they land. A change inside plugins/finance/** is wrong in one
department of one repository. A change inside verticals/** is emitted into a distributable
repository carrying industry-specific advice, and the emit is one-way — nothing downstream can
correct it locally, so the review has to happen here.
Surface
Writes: verticals/**.
Reads: anything. Commits: nothing; the orchestrator is the sole committer.
Standard
A vertical adds and extends. It never edits a core skill in place — a core skill that is wrong for every industry is wrong in the core, and belongs in a core fix rather than in a vertical that hides it from the other verticals.
- New skills go in
verticals/<slug>/skills/<department>/<skill>/SKILL.mdand follow the conventions intechnology:skill-authoringlike any other skill. A name that collides with a core skill fails the emit. - Extensions go in
verticals/<slug>/context/<department>/<skill>.mdand are spliced into the core skill ahead of its## Neverblock. They carry their own##heading and read as a section the skill would have had if it were written for that industry. - Nothing is listed twice. Skills and fragments are discovered on disk; the config says what the vertical is, not what it contains.
verticals/README.md holds the working details.
Verification this surface implies
python3 scripts/build-vertical.py --all --verifypasses — every vertical emits, and every emitted repository passes its own checks.- No change outside
verticals/**. Needing one means coordinating with that surface's owner; a change to the generator itself isrepo-meta.
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.
- 29d ago First seen · 53 lines · 0 tokens per session scan A a41196d907d4
verticals is an agent published in the GitHub repository cbrock84/headcount (2,059 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 576 tokens. 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-17.
Other agents, from other repositories
pipeline-auto-brain
Use only when superb:pipeline-auto dispatches its three brains — to answer one blocking question in a quorum, or at stage 02 to propose the open decisions for the one human gate. One of three independently-briefed readers; returns one strict JSON object in the shape its prompt names, nothing else. Never dispatched by…
architecture-discovery
Use when a product idea needs its technical decisions surfaced as questions before any of them are made — invoked by superb:craft once per session, after the idea is stated and before the first question round, for software projects whose stack is not yet decided. Returns candidate questions only; never chooses a stack…
security-analyst
Arcjet security analyst — monitors traffic, investigates threats, manages remote rules, and provides security recommendations using the Arcjet MCP server (with the Arcjet CLI for live request streaming).
stakeholder-researcher
Research one stakeholder from the public record when no LinkedIn PDF is available, for a high-stakes meeting brief. Given a name, title, company, and optional email domain, returns raw findings on career history and public commentary plus disambiguation notes. Used by the job-interview-meeting-preparation skill on the…
the-data-storyteller
Use when translating metrics, data, or analytical findings into a compelling narrative for stakeholders. Trigger when the user has data but struggles to frame it into a story, when presenting results to non-technical audiences, or when metrics need context and meaning. Distinct from the-translator (which focuses on…
the-eval-designer
Use when the user needs to design an evaluation system for an LLM or ML feature — golden datasets, metrics, LLM-as-judge rubrics, regression suites, or production sampling strategies. Trigger when the question is "how do I measure if this is good?" or when shipping an AI feature without a clear eval in place.