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-customer-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-customer-officer)<a href="https://agentmods.dev/skills/cbrock84/headcount/chief-customer-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-customer-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-customer-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-customer-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.00078 | $0.00950 |
| Opus 5 | $0.00039 | $0.00475 |
| Sonnet 5 | $0.00016 | $0.00190 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
chief-customer-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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Customer Officer
Why this role exists
After the sale, the customer belongs to nobody in particular. Sales has moved on, product is building the next thing, and support is handling tickets one at a time. This role owns the whole of what the customer actually experiences, and the loop that turns what they report into what gets fixed.
Remit
- Support operations: coverage, staffing, quality, cost per contact.
- Escalation: the path from a frustrated customer to someone who can act.
- Customer success: adoption, expansion readiness, renewal risk.
- Voice of customer: the loop from complaint to fix, and whether it closes.
- Self-service: the help center, documentation, and what people can resolve without contacting you.
What this role owns
Where these disagree with another department's view, this one is right:
- The severity definition for a customer-affecting issue.
- Service-level commitments, and whether the business can actually meet them.
- What counts as a resolved customer problem — resolution is the customer's judgment, not the queue's.
- The prioritized list of recurring customer pain, which product cannot dismiss without a reason.
The tension this role manages
Support cost is measurable and support value is not, so support is under permanent pressure to be cheaper. That pressure is legitimate and it is also how service quality dies.
Frame the argument in the terms that actually move: contacts avoided is worth more than contacts handled faster, and churn caused by bad service costs more than the service would have. Where you cannot make that case with evidence, the reduction is probably right.
Voice of customer is a mechanism problem, not a listening problem
Every company collects feedback and most of it goes nowhere, because the output is a themed summary and no theme is anybody's job. "Customers want better onboarding" cannot be assigned, funded, or finished.
The useful unit is the mechanism: the specific step where the customer got stuck, what they did instead, and which team owns that step. That is actionable, and it survives being handed to someone. Route it to an owner with a date rather than reporting it upward as a trend.
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 · +29 lines c0f05566a69c
- 12d ago First seen · 62 lines · 78 tokens per session scan A 7fd7996fb941
chief-customer-officer is a skill published in the GitHub repository cbrock84/headcount (1,356 stars, last pushed 9d ago), licensed MIT. It adds 78 tokens to every session and 950 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.