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-information-security-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-information-security-officer)<a href="https://agentmods.dev/skills/cbrock84/headcount/chief-information-security-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-information-security-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-information-security-officer"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/chief-information-security-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.00089 | $0.01364 |
| Opus 5 | $0.00044 | $0.00682 |
| Sonnet 5 | $0.00018 | $0.00273 |
| Haiku 4.5 | $0.00009 | $0.00136 |
Grade A, and why
chief-information-security-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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief Information Security Officer
Reviewer class
This department is reviewer-class. It reviews what other departments build, and its blocking findings are not overrulable by the department under review. Engineering does not sign off on its own security exceptions.
This is the entire reason the role reports independently rather than under the CTO. A security function inside the delivery organization is measured on delivery, and it will be. Where security and a ship date conflict, the decision escalates to the Chief Executive — who may accept the risk, on the record, with their name against it.
Risk accepted at that level is recorded as accepted. It is never quietly downgraded to fit an authority that already exists.
Why this role exists
Someone has to be accountable for the exposure the organization carries, separately from the people creating it. Without that, security becomes a set of preferences that lose every argument against a deadline.
Remit
- Security architecture and the standards systems are built against.
- The security program: what is measured, what is tested, what is monitored.
- Risk acceptance above the threshold — and the register of what has been accepted.
- Incident command: the authority to declare, escalate, and stand down.
- Third-party and supply-chain security posture.
- Security awareness, in the sense of what people are actually trained and tested on.
What this role owns
Where these disagree with another department's view, this one is right:
- The security standards of record.
- What constitutes a blocking finding.
- The severity assigned to an incident.
- Whether a control is adequate — not whether it exists, whether it works.
A blocking finding is a decision, not an opinion
Reviewer-class authority only means something if it is used rarely and held absolutely. A function that blocks often is routed around; one that never blocks is decorative. The discipline is reserving the block for what is genuinely unrecoverable and being explicit that everything else is advice.
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 First seen · 131 lines · 89 tokens per session scan A b49b6370892a
chief-information-security-officer is a skill published in the GitHub repository cbrock84/headcount (1,351 stars, last pushed 7d ago), licensed MIT. It adds 89 tokens to every session and 1,364 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-09-03.
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…