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-statement-analysisgit 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-statement-analysis)<a href="https://agentmods.dev/skills/cbrock84/headcount/financial-statement-analysis"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/financial-statement-analysis/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-statement-analysis"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/financial-statement-analysis.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.00093 | $0.01020 |
| Opus 5.5 | $0.00037 | $0.00408 |
| Sonnet 5.5 | $0.00019 | $0.00204 |
| Haiku 4.5 | $0.00009 | $0.00102 |
Grade A, and why
financial-statement-analysis 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Financial statement analysis
The statements tell you what happened. Analysis tells you why, and whether it continues.
Read the three statements against each other
A single statement is almost never enough. The income statement reports profit, the cash flow statement reports cash, and the gap between them is usually the story.
- Net income rising while operating cash flow falls is the signal worth chasing first. It means working capital is absorbing the growth, or revenue is being recognized ahead of collection.
- The balance sheet is a point in time; the other two cover a period. Comparing a period figure to a point-in-time balance without averaging the balance overstates efficiency ratios.
- Read the notes. Concentration of customers, debt maturities, commitments, related parties, and subsequent events routinely matter more than anything on the face of the statements.
Do fluctuation analysis before you compute a single ratio
Compare against the prior period and against budget. They answer different questions: prior period tells you what changed, budget tells you whether you understood your own business.
- Set a threshold in both currency and percent. Percent alone sends you chasing large swings on small accounts; currency alone hides a small account that doubled.
- Explain with a driver, not a restatement. "Revenue up 12%" is the observation, not the explanation. Volume, price, mix, timing, and one-off items are explanations.
- Track how many variances you cannot explain. A close where three material movements have no owner is telling you something about the underlying records, not about performance.
Compute ratios against the question you actually have
- Profitability — gross margin, operating margin, net margin, return on invested capital.
- Liquidity — current and quick ratio, and the one that usually matters more in practice, days of cash on hand.
- Leverage and solvency — debt to EBITDA, interest coverage, debt to equity.
- Efficiency — days sales outstanding, days payable outstanding, days inventory outstanding, and the cash conversion cycle they combine into.
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 b85fb99b537d
- 1mo ago First seen · 81 lines · 93 tokens per session scan A f0e89aaa66eb
financial-statement-analysis is a skill published in the GitHub repository cbrock84/headcount (2,075 stars, last pushed 2d ago), licensed MIT. It adds 93 tokens to every session and 1,020 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
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.
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.
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.