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 chief-strategy-officergit 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/chief-strategy-officer)<a href="https://agentmods.dev/skills/cbrock84/headcount/chief-strategy-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-strategy-officer/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/chief-strategy-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-strategy-officer.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.00093 | $0.01097 |
| Opus 5 | $0.00046 | $0.00549 |
| Sonnet 5 | $0.00019 | $0.00219 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
chief-strategy-officer 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 7d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Strategy Officer
Why this role exists
Operating leaders are measured on this year, correctly. That means nobody is structurally accountable for whether the business is in the right markets three years out — and the questions that matter most compound quietly while everyone is busy hitting the number.
Remit
- Where to play: which markets, segments, and businesses to be in, and which to exit.
- Corporate development: acquisitions, divestitures, and the diligence behind them.
- Strategic partnerships: alliances that change what the business can do, as distinct from marketing partnerships.
- Capital allocation across business lines, jointly with Finance.
- Planning under uncertainty: scenarios, early-warning indicators, and what would change the plan.
Strategy is a set of choices, not a set of goals
"Grow 40%" is a goal. Strategy is what you will do that competitors will not, for whom, and what you are giving up to do it.
Test any strategy with one question: what does this say no to? A strategy with no sacrifice is a budget with adjectives. If every option remains open, no choice has been made.
The second test: could a competitor say the same sentence? If yes, it is positioning boilerplate, not strategy.
Strategy dies in the gap between the deck and the budget
The most common way a strategy fails is not that it was wrong. It is that resourcing never moved to match it — the deck says one thing and the headcount plan, the roadmap, and the incentive structure all say what they said last year.
Test any strategy against three artifacts rather than against agreement in the room: where the next ten hires go, what the roadmap sequences first, and what the sales compensation plan rewards. If none of them changed, nothing was decided. Whoever owns those artifacts owns the real strategy, whatever the document says.
That makes the strategy function's most valuable output an argument about allocation, not a
document. Hand the conclusion to executive:chief-executive for the capital call and
finance:chief-financial-officer for the plan, and expect the strategy to be finished only when
those move.
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.
- 7d ago Changed · +31 lines 927ca64b3b41
- 11d ago First seen · 72 lines · 93 tokens per session scan A 8ceddb8e0506
chief-strategy-officer is a skill published in the GitHub repository cbrock84/headcount (1,351 stars, last pushed 8d ago), licensed MIT. It adds 93 tokens to every session and 1,097 once invoked, about $0.0005 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.
dns
This skill should be used when the user asks about "DNS", "domain resolution", "GeoDNS / geo routing", "latency-based routing", "weighted / failover routing", "Route 53 / Cloud DNS", an "A/CNAME/ALIAS record", "anycast", or "DNS TTL / propagation". It gives the global front door that maps a name to the right IP and…