by cbrock84
An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs in Claude Code and ChatGPT.
# Add to your Claude Code skills
git clone https://github.com/cbrock84/headcountLast scanned: 8/30/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-08-30T09:47:38.312Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how headcount compares with popular alternatives.
headcount is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by cbrock84. An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs in Claude Code and ChatGPT. It has 2,042 GitHub stars.
Yes. headcount passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/cbrock84/headcount" and add it to your Claude Code skills directory (see the Installation section above).
headcount is primarily written in Markdown. It is open-source under cbrock84 on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh headcount against similar tools.
No comments yet. Be the first to share your thoughts!
30 days in the Featured rail · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
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.
/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.
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.
| Skill | What it does |
|---|---|
agent-hierarchy |
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, an…. |
ai-research-analyst |
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in…. |
business-growth-consultant |
Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could…. |
ceo-advisor |
Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for i…. |
chief-executive |
Sets direction, allocates capital and attention, and makes the calls no one else can make. |
fundraising-and-investor-relations |
Raises capital and manages the relationship afterward — deciding how much and why, understanding what dilution and preferences actually cost, running a process with…. |
saas-idea-validator |
Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather than encourageme…. |
| Skill | What it does |
|---|---|
ai-workflow-architect |
Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fi…. |
api-design |
Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. |
branch-and-worktree-workflow |
Isolates feature work in its own branch or worktree and integrates it cleanly when done. |
chief-technology-officer |
Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. |
cloud-infrastructure |
Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. |
code-review |
Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. |
completion-verification |
Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rathe…. |
data-migration |
Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and parallel-run cutover,…. |
implementation-planning |
Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. |
observability-and-reliability |
Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. |
parallel-agent-delivery |
Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. |
prompt-optimizer |
Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it across models. |
release-and-deployment |
Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. |
skill-authoring |
Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do. |
solution-architecture |
Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. |
solution-exploration |
Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeof…. |
systematic-debugging |
Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. |
technical-debt-management |
Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. |
test-driven-development |
Drives implementation by writing a failing test first, then the smallest code that passes it. |
| Skill | What it does |
|---|---|
access-and-identity |
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. |
chief-information-security-officer |
Owns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work that creates unacc…. |
data-protection-and-encryption |
Protects data itself rather than the systems around it — classifying what you hold, encrypting in transit and at rest and understanding what each actually defends a…. |
detection-and-monitoring |
Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on…. |
incident-response |