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 operating-cadencegit 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/operating-cadence)<a href="https://agentmods.dev/skills/cbrock84/headcount/operating-cadence"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/operating-cadence/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/operating-cadence"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/operating-cadence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 51 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00095 | $0.00775 |
| Opus 5.5 | $0.00038 | $0.00310 |
| Sonnet 5.5 | $0.00019 | $0.00155 |
| Haiku 4.5 | $0.00010 | $0.00077 |
Grade A, and why
operating-cadence 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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating cadence
Every organization has a cadence. Most have one that accumulated — a meeting added after each incident, none ever removed — rather than one that was designed. The symptom is familiar: full calendars, thorough reporting, and decisions that still take six weeks.
Give every recurring meeting a decision it exists to make
A review that only shares information is a document pretending to be a meeting. Before a meeting recurs, answer three questions: what decision does this forum make, who in the room can make it, and what would have to be true for the answer to be no.
If a forum has made no decision in a quarter, either it is the wrong forum or the decision is being made elsewhere. Both are worth knowing.
Separate the three time horizons, and do not let them merge
- Weekly — execution. What is off track, what is blocking it, who is unblocking it by when. Short, operational, no strategy. Fifteen items at five minutes each, not five at fifteen.
- Monthly — performance. Results against plan, with the variance explained by a driver rather than restated. This is where a trend gets caught while it is still cheap.
- Quarterly — direction. Whether the plan is still the right plan, resource reallocation, and the deliberate stopping of things.
The common failure is a monthly review that fills with weekly firefighting, so nobody ever looks up. The fix is not discipline in the room; it is a functioning weekly meeting that leaves nothing urgent for the monthly one to absorb.
One set of numbers, owned by name
The same metric presented two ways in two forums will be argued about in both. Each metric needs a single definition, a single source, and one named owner who is accountable for the number rather than for the outcome it measures — those are different people surprisingly often, and the distinction stops reporting from becoming advocacy.
Publish the pack before the meeting and expect it read. A review that spends its first half being presented to has cut its own decision time in half.
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.
- 1mo ago First seen · 67 lines · 95 tokens per session scan A 802e2b7b9407
operating-cadence is a skill published in the GitHub repository cbrock84/headcount (2,080 stars, last pushed 4d ago), licensed MIT. It adds 95 tokens to every session and 775 once invoked, about $0.0004 per session on Opus 5.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
user-story-map
Build an interactive, drag-and-drop user story map so the user can re-slice work across release phases. Use when the user wants a story map, a phased roadmap, release slicing, a backbone/activities journey map, or to decide "which stories go in which phase" and move them around.
agile-ledger
Plain-Markdown Scrum / Agile product-management system for Claude Code. Manage a product backlog of Epics and User Stories, plan and run sprints, drive a board, track velocity, cut Major.Minor releases, and keep GitHub branches/commits/PRs traceable to stories — all from slash commands, with no Jira and no database.…
agile-ledger-workspace
Owns the Agile-Ledger ledger repository — the separate repo that holds one folder per code repo, so code repos stay clean. Create the ledger repo, register repositories into it, migrate a pre-2.0 in-repo Agile-Ledger/ folder, discover repositories on a GitHub org (including ones nobody told you about), run a single…
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
bug-investigate
Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing …
diagnose-project
Diagnose .NET SDK, restore, build, test, package, target framework, F# compile-order, C# analyzer, and project-reference failures with concrete next checks.