Headcount
An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs…
Install
/plugin marketplace add cbrock84/headcountInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →headcount
Add a department, not a prompt.
Open the interactive org chart — search every skill, open a department, jump to the source.
An agent organization structured as a company: a chief executive over 16 departments, 172 skills in total.
Every department is an independently installable plugin, so a project loads only the functions it needs rather than all of them at once.
Install
/plugin marketplace add cbrock84/headcount
/plugin install security@headcount
ChatGPT and Codex — the same repository. Add it as a plugin marketplace, or drop the
department you want into .agents/skills/ in your own project.
The skills are identical in both; only the manifests differ, and both sets are generated from
this tree, so a fix reaches both at once. See AGENTS.md.
Install as many departments as the project needs. Skills are addressed as department:skill —
security:threat-modeling, finance:unit-economics — so names never collide.
Use
Skills load themselves when a request matches. Ask a question in the department's territory and the right specialist engages:
| You ask | What loads |
|---|---|
| "why isn't this landing page converting?" | demand-generation:landing-page-cro-expert |
| "review this design before we build it" | security:threat-modeling |
| "can we afford this hire?" | finance:unit-economics |
| "our growth has stalled" | executive:business-growth-consultant |
Invoke one directly by name when you want a specific lens: /finance:financial-modeling.
New to this? docs/GETTING-STARTED.md covers which departments to install first, the three ways to invoke a skill, and what reviewer-class departments do differently.
Eleven situations that cross departments — a SOC 2 demand from an enterprise prospect, a link down between two sites, a renewal that auto-renewed because nobody owned the date — are worked through end to end in docs/USE-CASES.md, including what comes back and where a reviewer-class department stops the work rather than adding an opinion.
Each department also ships an agent charter in .claude/agents/, so a department can be delegated
to as a subagent with its own exclusive write surface.
Departments
Office of the CEO (Chief Executive) — 7 skills
Similar plugs
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…
Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.
Production-grade engineering skills for AI coding agents.
The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…