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 fundraising-and-investor-relationsgit 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/fundraising-and-investor-relations)<a href="https://agentmods.dev/skills/cbrock84/headcount/fundraising-and-investor-relations"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/fundraising-and-investor-relations/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/fundraising-and-investor-relations"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/fundraising-and-investor-relations.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 34 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.00091 | $0.01002 |
| Opus 5 | $0.00046 | $0.00501 |
| Sonnet 5 | $0.00018 | $0.00200 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
fundraising-and-investor-relations 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fundraising and investor relations
Capital is bought, not received, and the terms matter more than the headline number. So does what happens for the years afterward, which is where most of the relationship actually lives.
Financing terms have legal and tax consequences that vary by structure and jurisdiction. Get qualified counsel and your accountant on any instrument before signing.
Decide the amount from the plan, not from the market
Raise against what the money buys: the milestones that will make the next raise possible, plus enough runway to reach them and to be wrong once. Working back from milestones gives a number you can defend and a story that connects the raise to the outcome.
Raising more than the plan needs is not free — it costs dilution now and sets a valuation you have to grow into. Raising too little is worse, because running out mid-plan is the weakest possible negotiating position and everyone on the other side of the table knows it.
Understand what the terms cost, because valuation is the least of them
A high valuation with punishing terms is worse than a lower one with clean terms, and founders routinely trade the second for the first because only the first is quotable.
- Liquidation preference determines who gets paid first and how much before common shares see anything. A participating preference or a multiple can mean an apparently good exit returns little to founders and staff.
- Anti-dilution decides what happens if the next round is lower. The broader forms can shift ownership substantially in exactly the circumstances where you can least afford it.
- Board composition and protective provisions determine what you can do without asking. This is control, and it is permanent in a way valuation is not.
- Option pool sizing placed before the investment dilutes existing holders only. Where the pool sits in the calculation is a real price negotiation dressed as an administrative detail.
Model the outcome at several exit values, not just the good one. The terms that matter most only express themselves in the mediocre cases, which are the most likely ones.
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 First seen · 87 lines · 91 tokens per session scan A 31ddc58f505b
fundraising-and-investor-relations is a skill published in the GitHub repository cbrock84/headcount (1,356 stars, last pushed 9d ago), licensed MIT. It adds 91 tokens to every session and 1,002 once invoked, about $0.0005 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
stockbit-auth
Log in to Stockbit and capture the session for this server — opens the browser login flow and verifies the token was stored. Use when the user asks to log in or re-authenticate to Stockbit, or after a status check reports the session expired, HTTP 401, or logged out.
morning-scan
The pre-open and first-hour routine for IDX — session state, movers, a scan over a universe, and a catalyst check on the leaders. Use when the user asks what is moving today, for a morning briefing, or what to watch.
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.
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.
swiftui-app-architecture-workflow
Guide SwiftUI app-structure decisions for Apple apps across App, scenes, commands, focus, environment, preferences, window and document coordination, and reusable view composition. Use when the user wants help deciding where ownership belongs in a SwiftUI app, which data-flow mechanism fits a responsibility, or how to…