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 agentmods add skills/cbrock84/headcount/market-entrynpx skills add cbrock84/headcount --skill market-entrygit 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/market-entry)<a href="https://agentmods.dev/skills/cbrock84/headcount/market-entry"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/market-entry.svg" alt="Measured on agentmods" height="20"></a>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.00900 |
| Opus 5 | $0.00046 | $0.00450 |
| Sonnet 5 | $0.00019 | $0.00180 |
| Haiku 4.5 | $0.00009 | $0.00090 |
Grade A, and why
market-entry 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 2d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market entry
Entry decisions are usually made on the size of the opportunity and lost on the cost of serving it. The market was real; what was underestimated was everything required to operate there.
Size from the bottom up, then check it against the top down
A market report gives you a number that includes companies who will never buy from you. Build the estimate from countable things: how many organizations fit your profile, how many have the problem acutely, what they spend on it today, what share you could plausibly hold in a defined period.
Use a top-down figure only as a sanity check. If bottom-up and top-down differ by an order of magnitude, one of them contains an assumption nobody has stated, and finding it is the most valuable hour in the analysis.
Test whether the advantage actually transfers
The question is not whether the market is attractive — attractive markets are attractive to everyone, including incumbents already there. The question is what you have that wins.
Advantages transfer unevenly. Product capability usually transfers. Brand rarely does across geographies. Distribution and relationships almost never do. Cost structure may invert entirely. An entry justified by "we are strong in the adjacent market" needs to name the specific thing that carries over, and it is usually less than assumed.
Ask why the incumbent has not already done what you plan to do. Either they cannot, which is your advantage, or they have found it does not work, which is your warning.
Choose the entry mode against speed, control and reversibility
- Organic — full control, slowest, and every local capability has to be built. Right when the advantage is the product and the market is reachable with your existing motion.
- Partnership or distribution — fast and cheap, and you learn less. Right when local relationships are the barrier and you can accept less control of the customer relationship.
- Acquisition — buys presence and capability immediately, at the highest price and with the integration risk. Right when time matters more than money and the target has something you cannot build quickly.
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.
- 2d ago First seen · 80 lines · 93 tokens per session scan A eb8d559c94f5
market-entry is a skill published in the GitHub repository cbrock84/headcount (1,247 stars, last pushed 2d ago), licensed MIT. It adds 93 tokens to every session and 900 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
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.
mode
Show or set NeatContext routing to auto, ask, or manual for Codex, with an optional default shared with every other NeatContext host. Use only when the user explicitly invokes this skill or clearly asks to change routing behavior.
status
Report the NeatContext context and routing mode active in Codex, including missing-file or stale-routing warnings. Use when the user asks which context is connected or explicitly invokes this skill.
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.
dns
This skill should be used when the user asks about "DNS", "domain resolution", "GeoDNS / geo routing", "latency-based routing", "weighted / failover routing", "Route 53 / Cloud DNS", an "A/CNAME/ALIAS record", "anycast", or "DNS TTL / propagation". It gives the global front door that maps a name to the right IP and…