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.
Borrowing it
Nothing to install: this file belongs to cbrock84/headcount. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cbrock84/headcount/main/AGENTS.mdgit 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/instructions/cbrock84/headcount/agents-md)<a href="https://agentmods.dev/instructions/cbrock84/headcount/agents-md"><img src="https://agentmods.dev/badge/instructions/cbrock84/headcount/agents-md/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/instructions/cbrock84/headcount/agents-md"><img src="https://agentmods.dev/badge/instructions/cbrock84/headcount/agents-md.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.00745 | $0.00745 |
| Opus 5.5 | $0.00298 | $0.00298 |
| Sonnet 5.5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
headcount AGENTS.md 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.
AGENTS.md
An agent organization structured as a company: 16 departments, 172 skills, each department installable on its own.
This file describes the repository to an agent working on it. The skills under plugins/ are a different thing — they describe how to do the work of a function, and they load when a request matches their description.
Installing, in either tool
The skills are identical. Only the manifests differ, and both are generated from the same tree, so a skill fixed once is fixed for both.
| Manifests | |
|---|---|
| Claude Code | plugins/<department>/.claude-plugin/plugin.json, .claude-plugin/marketplace.json |
| ChatGPT / Codex | plugins/<department>/.codex-plugin/plugin.json, .agents/plugins/marketplace.json |
Before you open a pull request
./scripts/check-all.sh
Every check CI runs, in one script — the workflow calls this same file, so the two cannot drift. Stage new files first: the surface guard reads git ls-files, so an unstaged file is invisible to it and the check passes locally then fails in CI.
Rules that are enforced rather than suggested
- One owner per path.
docs/AGENT-SURFACES.mdmaps every tracked path to exactly one agent, and no two owners may claim the same path. A new department adds its roster row, its surface block and its charter in the same change. - Generated files are never hand-edited. The README, the org chart, the social card, each skill's
references/sources.md, and these manifests are all emitted from the tree and verified with--check. An edit to one is lost on the next regenerate. - Sources are references, never copies.
sources/*.tomlmaps outside authorities to the skills they settle questions for, andscripts/build-sources.pyemits each skill's list into its ownreferences/sources.md. Thelicensefield decides whether an agent may quote a source or only cite it — most of what a professional must cite is not open, so when torn between two classes take the more restrictive one. - Verticals emit one way.
verticals/<slug>/plus the core emits a standalone repository viascripts/build-vertical.py. Generated output is never hand-edited and is not committed;--verifyemits to a temporary directory and runs the emitted repository's own checks instead. - US English, by exact word form.
scripts/check-us-english.py --fixrewrites. It leaves URLs alone, which it did not always do. - No third-party licensed content. All prose here is original;
scripts/check-provenance.pyis the backstop.
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 · 745 tokens per session scan A 5e6721bdca90
headcount AGENTS.md is an instructions file published in the GitHub repository cbrock84/headcount (2,059 stars, last pushed 28d ago), licensed MIT. It adds 745 tokens to every session, about $0.0030 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).