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 portfolio-strategygit 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/portfolio-strategy)<a href="https://agentmods.dev/skills/cbrock84/headcount/portfolio-strategy"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/portfolio-strategy/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/portfolio-strategy"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/portfolio-strategy.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.00074 | $0.00703 |
| Opus 5 | $0.00037 | $0.00351 |
| Sonnet 5 | $0.00015 | $0.00141 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
portfolio-strategy 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 5d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portfolio strategy
Most organizations fund by inertia. Last year's allocation plus a percentage, adjusted by who argued hardest. Portfolio strategy is the discipline of deciding again, deliberately.
Assess each line on two axes
Attractiveness — is this a good place to be? Market size and growth, structural profitability, concentration of buyer power, regulatory direction, and how the economics behave as it scales.
Right to win — is it good for us? Our position relative to alternatives, the assets or capabilities that transfer, and whether the advantage is durable or borrowed.
The combination gives you four postures, and the honest one is usually uncomfortable:
- Attractive, we can win — fund properly. Underfunding these is the most common and most expensive portfolio error.
- Attractive, we cannot win — the seductive trap. Everyone wants in on a good market. Entering without an advantage funds someone else's growth.
- Unattractive, we can win — harvest. Run for cash, do not invest for growth.
- Neither — exit. Slowly and reluctantly is how these consume a decade of attention.
Judge on marginal return, not absolute size
The question is never "is this business good." It is "what does the next dollar do here versus elsewhere." A large profitable line may be a poor place for incremental investment; a small one may be the best.
Watch for cross-subsidy. A weak line supported by a strong one is a decision, and it should be an explicit one with a thesis and an end date — not an accident nobody has looked at.
Exit is the hardest decision and the most valuable
Sunk cost, internal advocates, and the discomfort of admitting a bet failed all argue for one more year. The test is prospective: knowing what we know now, would we start this today? If not, the only question is how to exit well.
Exiting frees more than the money. It frees the attention of the people running it, which is usually the scarcer resource.
Plan exits properly: customer commitments, employee treatment, and contractual obligations. A badly run exit costs more than the business was losing.
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.
- 5d ago Changed · +7 lines e4cd87e30b66
- 9d ago First seen · 61 lines · 74 tokens per session scan A 9ada16c4592d
portfolio-strategy is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 5d ago), licensed MIT. It adds 74 tokens to every session and 703 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-08-30.
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.
xcode-coding-intelligence-workflow
Guide Xcode coding-intelligence setup, ACP-hosted agents, external-agent access through xcrun mcpbridge, permissions, Xcode-only agent configuration, and stable or beta agentic workflows.