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 financial-reporting-and-closegit 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/financial-reporting-and-close)<a href="https://agentmods.dev/skills/cbrock84/headcount/financial-reporting-and-close"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/financial-reporting-and-close/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/financial-reporting-and-close"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/financial-reporting-and-close.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.00069 | $0.00800 |
| Opus 5.5 | $0.00028 | $0.00320 |
| Sonnet 5.5 | $0.00014 | $0.00160 |
| Haiku 4.5 | $0.00007 | $0.00080 |
Grade A, and why
financial-reporting-and-close 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Financial reporting and close
A close is a manufacturing process whose output is a number people will make decisions on. Treat it as a process — sequence, dependencies, quality control — and it gets faster and more accurate together, which sounds contradictory only if you think speed comes from cutting checks.
Design the close as a critical path
Map every task with its owner, its dependencies and its duration. Most closes are slow because independent work is running in series out of habit, not because any step is long.
Move work out of the close window wherever it does not depend on period-end: reconcile subledgers continuously, book recurring accruals from a schedule, prepare consolidation structure in advance. Anything you can do on day minus three is a day you are not doing on day two.
Set a hard cutoff and hold it. A close that stays open for late entries never finishes and teaches everyone that deadlines are advisory.
Reconciliations are the control
Every balance sheet account gets an owner and a reconciliation. The reconciliation is not the schedule — it is the explanation of the difference and what will clear it.
Watch aged reconciling items specifically. An unexplained item that has survived three closes is not a timing difference; it is an error that has been carried forward by people assuming someone else understood it.
Accruals and the honesty of estimates
Accrue on the best available evidence and document the basis. The basis matters more than the number, because next period someone has to decide whether it still holds.
Track how estimates resolve against actuals. Consistent bias in one direction is information about the estimator or the process, and it is invisible unless someone looks.
Reporting that gets read
Explain variance against a stated expectation — budget, prior period, or forecast — and say which. A variance without a baseline is a number.
Lead with the two or three things that changed and why, then supporting detail. A report that requires the reader to find the story does not get read, and its absence of readership is discovered during a crisis.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +7 lines 18fed0ea27c2
- 1mo ago First seen · 69 lines · 69 tokens per session scan A 9853e7ddb3aa
financial-reporting-and-close is a skill published in the GitHub repository cbrock84/headcount (2,065 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 800 once invoked, about $0.0003 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
launch-google-search
Launch a complete Google Ads Search campaign — campaign, ad group, responsive search ads, keywords, sitelinks, callouts, and negatives — built paused and ready to review. Use when the user wants to spin up a new Search campaign on Google Ads.
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
rotate-creative
Pause fatigued ads and ship fresh creative variants in their place. Works on both Meta and Google Ads. Use when CTR is dropping, frequency is climbing, or the user says "creative is tired" / "let's refresh ads". Always starts new variants paused.
spend-audit
Audits a Webshare account for wasted proxy spend and recommends plan adjustments based on the account's own historical usage, using the webshare CLI. Use periodically (e.g. monthly) or whenever asked to review proxy costs, find savings, cut spend, or right-size plans. Strictly read-only — it recommends, it never…
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.
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.