headcount: ChalupaBrock's MIT "Org in a Box" Claude Skill Set (2026)

Roughly three days before this post, a thread on r/claudeskills crossed ~1.6K upvotes for something unusually ambitious: not another single-purpose agent skill, but an entire company org chart packaged as one MIT-licensed repository. ChalupaBrock (@cbrock84) calls it headcount — tagline "Add a department, not a prompt" — and describes it as 25+ years of corporate and tech leadership distilled into 16 departments and 172 SKILL.md specialists you can install à la carte in Claude Code.

If you've been following graph engineering — the idea that multi-agent systems need a programmable org graph, not just better loops — headcount is the most literal open-source answer yet: CEO lane, CISO lane, HR lane, each with per-role skills, written authority levels, and CI checks that keep departments from stepping on each other's write surfaces.

TL;DR

What's inside: departments, not monoliths

headcount's core design choice is plugin-shaped departments rather than one giant skill dump. The README lists 16 departments spanning the Office of the CEO, Technology, Security, Product, Finance, People, Legal & Risk, Demand Generation, Customer Success, and more — 172 skills total at the time of writing.

Each department is an independently installable plugin. A solo founder might load Finance + People for headcount planning and comp bands; a security-conscious team adds Security without pulling in the entire catalog.

Skills load on intent — ask "can we afford this hire?" and finance:unit-economics engages; ask "review this design before we ship" and security:threat-modeling loads. You can also invoke directly: /finance:financial-modeling.

Every department ships an agent charter under .claude/agents/, so a department can be delegated as a subagent with its own exclusive write surface — the same pattern Arcads' Marketing OS uses for six marketing roles, but at company scale.

Reviewer-class authority

Two departments are reviewer-class: Security (CISO) and Legal & Risk (CLO/CCO). They review what other departments produce; blocking findings cannot be overridden by the department under review. The README explains why the CISO and CLO report to the chief executive rather than into the function they oversee — audit authority stays separate from execution authority.

That maps cleanly onto real org design and onto MCP security thinking: some lanes need stop-work power, not just advisory opinions.

agent-guard and the surface map

CI runs ./scripts/check-all.sh, which includes:

node plugins/executive/skills/agent-hierarchy/scripts/agent-guard.mjs check

The surface map check enforces that every tracked path has exactly one owner — no two departments claiming the same write surface. That is the mechanical backing for "exclusive write surface" language in the executive agent-hierarchy skill and a direct answer to the r/claudeskills thread debate about specialist guardrails vs. limitless LLM bloat: headcount bets on narrow lanes with enforced boundaries, not one omniscient prompt.

Other checks validate SKILL.md frontmatter, provenance (no third-party license text smuggled in), generated README/org-chart tables, and US English spelling — a unusually rigorous bar for a community skill repo.

What problems it actually covers

The r/claudeskills pitch and the repository README align on scope: building and running a company, not just writing code faster.

Seven cross-department scenarios — SOC 2 demands from enterprise prospects, security incidents, stalled funnels — are walked end-to-end in the project's use-case docs, including cases where a reviewer-class department stops work rather than adding another opinion.

Getting started (and where people get stuck)

Official path — Claude Code plugin marketplace:

/plugin marketplace add cbrock84/headcount
/plugin install security@headcount

Install only the departments your project needs. Address skills as department:skill.

Interactive org chart: the GitHub Pages org chart lets you search all 172 skills, open a department, and jump to source — useful before you install anything.

Installation confusion (Claude Desktop vs CLI)

The most common setup failure in community threads is treating headcount like a single file you drop into Claude Desktop. It is not a Desktop skill bundle — it is a Claude Code plugin marketplace with per-department installs and subagent charters. If you are on OpenAI Codex or Antigravity instead, check whether a community fork matches your harness before copying install commands verbatim. adixdbr's Codex/Antigravity port (with an upstream PR) is the named community effort from the Reddit thread — treat it as experimental until merged upstream.

MCP fills gaps the skills do not

The OP noted using ZipRecruiter and Indeed MCPs to fill org-chart gaps — posting roles, pulling market comp data, or syncing reqs skills structure but do not execute. That is the intended split: skills for playbooks, MCP for live integrations. Wire recruiting MCPs with the same least-privilege discipline you would use for any HR-facing tool.

SMB use case: admin without full headcount

The clearest non-enterprise pitch from the thread: small teams that need corporate functions occasionally — drafting a headcount plan, pressure-testing a offer band, running a lightweight threat model before a launch — without hiring a fractional CFO, CLO, and CISO on day one.

headcount does not replace those humans for regulated decisions. The contributing guide warns that skills touching law, privacy, compensation, medical, financial, or safety advice must say what they structure vs. what needs qualified professional input. Used honestly, it is a thinking scaffold and document accelerator — closer to Copilot Studio HR onboarding patterns than to autonomous HR software.

How it compares to other "agent org" projects

headcount is the most department-complete open package explainx.ai has seen for company operations. It is also the most install-heavy — 172 skills is a catalog, not a starter kit. Prefer loading two or three departments and expanding when triggers misfire.

What people are pushing back on (balanced take)

The upvote count reflects genuine interest; the comment section reflects genuine skepticism. Worth separating the threads:

Oversimplification. Corporate org design is context-heavy. A skill that returns a "verdict" on a SaaS idea or comp band is useful for first-pass structure, not board-ready advice. The README's regulated-ground warnings help, but nothing substitutes for domain counsel on material decisions.

No evals. Unlike Gary Tan's gbrain eval loop or production agent benchmarks, headcount ships authoring quality checks (frontmatter, surface map, provenance) — not outcome evals on whether finance:unit-economics produces correct models. You are trusting 25 years of encoded judgment, not measured accuracy.

Agentic org bloat. Installing all 16 departments because you can is the failure mode graph engineering warns about: context spent discovering skills, conflicting lanes, and ceremonial "CISO review" on every typo. headcount's plugin model and reviewer-class separation are designed to fight bloat — but only if you treat departments like hires, not like sticker collections.

Specialist guardrails vs. limitless LLM. The repo lands firmly on specialists: exclusive write surfaces, non-overridable reviewers, agent-guard ownership checks. Critics argue that rigid org charts fight the model's generalist strength. explainx.ai's read: for company operations — where audit trails and stop-work authority matter — the specialist bet is coherent. For exploratory coding, a lighter skill set wins.

Practical first steps

1. Open the interactive org chart and search for the two problems you hit weekly (e.g. "headcount plan", "threat model").
2. Install one builder department and one reviewer department if your work touches shipping code or contracts.
3. Run a real question through natural language first; only memorize department:skill names for repeat workflows.
4. If hiring is in scope, pair People/Finance skills with recruiting MCPs — scoped credentials, read-only where possible.
5. Before scaling, read docs/USE-CASES.md for cross-department flows so you know when Legal or Security is supposed to block, not advise.

Related on explainx.ai

• What are agent skills? Complete guide
• Graph engineering: multi-agent organizations
• Arcads Marketing OS — six-role Claude skill org
• MCP security guide
• OpenClaw agent architecture
• Codex + ChatGPT Work — 8M users
• Copilot Studio HR onboarding agent
• Top AI prompts for HR and recruiting
• Browse community skills on explainx.ai/skills

Repository structure, star count, department totals, and r/claudeskills engagement figures are accurate as of September 1, 2026. Verify install commands against the latest README before production use.