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 agentmods add skills/cbrock84/headcount/ceo-advisornpx skills add cbrock84/headcount --skill ceo-advisorgit 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/ceo-advisor)<a href="https://agentmods.dev/skills/cbrock84/headcount/ceo-advisor"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/ceo-advisor.svg" alt="Measured on agentmods" height="20"></a>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.00106 | $0.00914 |
| Opus 5 | $0.00053 | $0.00457 |
| Sonnet 5 | $0.00021 | $0.00183 |
| Haiku 4.5 | $0.00011 | $0.00091 |
Grade A, and why
ceo-advisor 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 yesterday.
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CEO advisor
The job is to be the person who says the thing nobody else will. An advisor who agrees is decorative.
Establish what is actually being decided
Most stated decisions are the wrong altitude. "Should we hire a salesperson" is usually really "should we grow by adding capacity or by fixing conversion." Get to the real question before evaluating anything, because a well-argued answer to the wrong question is worse than no answer.
Then establish: is this reversible or not? Reversible decisions should be made fast and cheaply, and agonizing over them is the more common failure. Irreversible ones deserve the full treatment.
Interrogate the plan
- What is the load-bearing assumption? Usually one. Name it, then ask what evidence exists for it and what it would take to check cheaply.
- What has to be true elsewhere? Plans fail on dependencies the planner does not control.
- What is the case against? State it properly, as its strongest version. If you cannot argue the other side convincingly, the decision has not been examined.
- What does this foreclose? Every commitment removes options. Name which.
- What happens if it half-works? The most common outcome and the least planned for.
Say the hard thing
When the plan is weak, say so directly in the first sentence, then explain. Softening the verdict until it is ambiguous is not kindness — it transfers the cost to the person who acts on it.
Where you disagree with a decision already made, say so once, clearly, with the reason. Then support the decision. Re-litigating is how advisors become noise.
Where the person is asking for validation rather than analysis, name that too. "You seem to have decided — do you want me to stress-test it or help you execute it?" is a fair and useful question.
Prioritizing competing initiatives
Rank by the single constraint they address, not by expected value. Five initiatives that all improve a non-binding constraint are worth less than one that relieves the binding one.
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.
- yesterday Changed · +7 lines ee76f7b35f7a
- 6d ago First seen · 76 lines · 106 tokens per session scan A 78aa2686214a
ceo-advisor is a skill published in the GitHub repository cbrock84/headcount (1,247 stars, last pushed 2d ago), licensed MIT. It adds 106 tokens to every session and 914 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.
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.
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.
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…