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 strategic-alliancesgit 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/strategic-alliances)<a href="https://agentmods.dev/skills/cbrock84/headcount/strategic-alliances"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/strategic-alliances/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/strategic-alliances"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/strategic-alliances.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.00081 | $0.00738 |
| Opus 5 | $0.00041 | $0.00369 |
| Sonnet 5 | $0.00016 | $0.00148 |
| Haiku 4.5 | $0.00008 | $0.00074 |
Grade A, and why
strategic-alliances 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 6d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategic alliances
Distinct from marketing partnerships. Those borrow an audience; these change what the business can do or where it can sell.
Partner, build, or buy
Partner when the capability is genuinely outside your core, the partner is materially better at it, and the arrangement can be unwound. Build when it is core, or when depending on someone else creates unacceptable exposure. Buy when you need control and speed and the thesis holds.
The question that decides it: what happens if this partner becomes a competitor, is acquired by one, or simply loses interest? If the answer is existential, do not partner — that is a build or buy decision wearing a cheaper price tag.
Structure by what each side actually wants
Partnerships fail on asymmetry of motivation more than on terms. Before structuring, establish what the partner gets, whether it is material to them, and who inside their organization is accountable for it.
A partnership that is strategically important to you and a rounding error to them will not be executed, whatever was signed. Being the small partner is workable — being the small and uninteresting partner is not.
Terms that determine whether it works
- Exclusivity — expensive, occasionally worth it, and always time-boxed. Perpetual exclusivity given away early is a recurring regret.
- Economics — who books revenue, on what split, and what happens to it if volume grows tenfold.
- Roadmap commitments — what each side will build and by when, with a remedy if they do not.
- Data — what flows where, under what basis, and what happens to it at termination.
- Customer ownership — who holds the relationship, and who may market to them afterward. Most disputed, most often left vague.
- Termination and transition — notice, and what continues for customers mid-contract. Negotiate the exit while everyone is friendly, because it will not be negotiable later.
Making it produce
Signed is not launched. Partnerships need a named owner on each side, a joint plan with dates, and a regular review that either side can bring problems to.
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.
- 6d ago Changed · +7 lines 46c91d2a158f
- 10d ago First seen · 62 lines · 81 tokens per session scan A 96e6c8640d1f
strategic-alliances is a skill published in the GitHub repository cbrock84/headcount (1,335 stars, last pushed 7d ago), licensed MIT. It adds 81 tokens to every session and 738 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
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…