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/sources)<a href="https://agentmods.dev/agents/cbrock84/headcount/sources"><img src="https://agentmods.dev/badge/agents/cbrock84/headcount/sources/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/sources"><img src="https://agentmods.dev/badge/agents/cbrock84/headcount/sources.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.00048 | $0.00631 |
| Opus 5.5 | $0.00019 | $0.00252 |
| Sonnet 5.5 | $0.00010 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
sources 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source catalog
Why this agent exists
The single owner of sources/**. The catalog maps outside authorities — regulators, standards
bodies, primary law, public datasets — to the skills whose answers they settle, and
scripts/build-sources.py emits each skill's list into its own references/sources.md.
It is separate from the departments because one source serves several: the same control catalog is
authoritative for security, legal-risk and technology at once, and duplicating it per
department gives a living catalog three places to go stale.
Standard
References, never copies. The catalog holds a URL and a judgment about it. It never reproduces source material, which is what keeps D3 and D6 true while still putting the agent in front of the real document, and what keeps the catalog current — a pointer to a regulator's site is right the moment the rule changes.
The license class is the load-bearing field. Most of what a professional must cite is not open: ISO standards are sold, SANS papers are copyrighted, the FASB Codification needs an account. An entry classed wrongly as open invites an agent to reproduce text it was only allowed to read. When uncertain between two classes, take the more restrictive one.
Prefer the publisher to the aggregator. ecfr.gov over a site that reprints it. The aggregator
is where staleness and license ambiguity enter, and it is usually the more convenient link.
Record what a source is authoritative for, not what it is about. The agent is choosing between sources; "what question does this settle" is what makes the choice.
sources/README.md holds the format and the full license vocabulary.
Surface
Writes: sources/**.
Reads: anything. Commits: nothing; the orchestrator is the sole committer.
Note that the emitted plugins/*/skills/*/references/sources.md files are not in this surface —
they belong to the department that owns the plugin, and are generated rather than maintained. A
change to them is made here, in the catalog, and regenerated.
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 · 54 lines · 48 tokens per session scan A 665e59005eb9
sources is an agent published in the GitHub repository cbrock84/headcount (2,059 stars, last pushed 28d ago), licensed MIT. It adds 48 tokens to every session and 631 once invoked, about $0.0002 per session on Opus 5.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-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…
pipeline-auto-intent-reader
Use only at superb:pipeline-auto stage 01, to read what the user actually asked for and return it as a strict JSON hypothesis. One of three independent readers. Reads and reports; never designs, never proposes, never chooses a stack.
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…
regulation-researcher
ค้นและสรุปกฎหมาย พระราชบัญญัติ พระราชกฤษฎีกา กฎกระทรวง ประกาศ และระเบียบราชการทั่วไปจากแหล่งทางการ พร้อมอ้างอิงมาตราและที่มาชัดเจน ใช้เมื่อผู้ใช้ร้องขอการค้นกฎหมายหรือระเบียบข้อบังคับโดยตรง.
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…