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.
npx skills add cbrock84/headcount --skill business-growth-consultantgit 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/skills/cbrock84/headcount/business-growth-consultant)<a href="https://agentmods.dev/skills/cbrock84/headcount/business-growth-consultant"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/business-growth-consultant/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/skills/cbrock84/headcount/business-growth-consultant"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/business-growth-consultant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.00839 |
| Opus 5 | $0.00041 | $0.00419 |
| Sonnet 5 | $0.00016 | $0.00168 |
| Haiku 4.5 | $0.00008 | $0.00084 |
Grade A, and why
business-growth-consultant 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 8d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business growth consultant
One thing limits growth at any moment. Work on anything else and the effort is absorbed with no output. The entire value of this skill is finding which one.
Diagnose the constraint first
Walk the chain in order and find the first place it breaks:
- Awareness — do enough of the right people know this exists?
- Interest — do they understand why it matters to them?
- Conversion — do they act?
- Delivery — do they get the value promised?
- Retention — do they stay?
- Economics — does each customer leave the business better off?
The constraint is usually not where attention is. Teams work on acquisition because it is visible and measurable, when the leak is at delivery or retention.
Two tells worth watching for:
- Rising revenue, flat profit — the constraint is economics, and growth is making it worse.
- Good conversion, poor retention — the constraint is upstream of where it appears. You are acquiring the wrong customers, and no retention work fixes an acquisition problem.
Then find the leverage
Against the identified constraint only, generate moves and rank them by impact ÷ effort × confidence. Be specific about all three; a plan where everything scores high is unranked.
Prefer moves that compound over moves that add. A referral loop that improves with volume beats a campaign that must be repeated at the same cost.
Sequencing
- Fix the constraint before scaling anything. Scaling a leaky funnel multiplies the leak.
- One initiative at a time when you cannot attribute results. Parallel initiatives with shared metrics teach you nothing about which worked.
- Set a read-by date and a kill threshold before starting.
Scaling readiness
Before recommending growth spend, check the business can absorb it: delivery capacity, support load, cash to fund the gap between acquisition and payback, and whether unit economics hold at volume. Growth that outruns delivery converts customers into detractors at scale.
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.
- 8d ago Changed · +7 lines e9a3964c6400
- 12d ago First seen · 78 lines · 81 tokens per session scan A 9d5d700219e4
business-growth-consultant is a skill published in the GitHub repository cbrock84/headcount (1,356 stars, last pushed 8d ago), licensed MIT. It adds 81 tokens to every session and 839 once invoked, about $0.0004 per session on Opus 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-08-30.
Other skills, from other repositories
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
mode
Show or set NeatContext routing to auto, ask, or manual for Codex, with an optional default shared with every other NeatContext host. Use only when the user explicitly invokes this skill or clearly asks to change routing behavior.
status
Report the NeatContext context and routing mode active in Codex, including missing-file or stale-routing warnings. Use when the user asks which context is connected or explicitly invokes this skill.
list
List the local NeatContext Contexts available to Codex. Use when the user asks what contexts exist, what can be connected, or explicitly invokes this skill.
build-oxpecker-web-app
Build or modify an Oxpecker web application in idiomatic F#, using endpoint routing, functional EndpointHandler and EndpointMiddleware composition, ASP.NET Core metadata, and focused endpoint tests.
go
Compatibility entry for Visual Stack's former /vstack:go command. Runs the wireframe and UI review tool, now called review. Use only when the user invokes /vstack:go.