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 partnership-marketinggit 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/partnership-marketing)<a href="https://agentmods.dev/skills/cbrock84/headcount/partnership-marketing"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/partnership-marketing/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/partnership-marketing"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/partnership-marketing.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.00059 | $0.00556 |
| Opus 5 | $0.00030 | $0.00278 |
| Sonnet 5 | $0.00012 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
partnership-marketing 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 7d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Partnership marketing
Borrowing an audience is the cheapest reach available and the easiest to do badly.
Affiliates sit next to this rather than inside it: they are a paid channel with commercial terms,
their own mechanics and their own fraud controls. revenue:referral-programs covers them.
Evaluating a partner
Fit matters more than size. The test is overlap of audience with non-overlap of offering: they serve the same people, and you do not compete for the same budget.
Check before committing:
- Audience overlap — same buyer, or merely same industry? Same industry is not enough.
- Engagement over follower count. A small responsive audience beats a large indifferent one, and follower counts are the easiest number to inflate.
- Their audience's trust in them. You are borrowing that, and you can spend it.
- What they get. A partnership that only serves you does not get executed, whatever was agreed.
Structuring
Write down, before anything ships: what each side produces, what each promotes and when, how leads or revenue are attributed, who owns the assets afterward, and what happens if one side does not deliver. Most partnerships fail on the last two, discovered late.
For creator deals specifically: pay for the work, not for promises about performance; require disclosure without exception; and give creative latitude — audiences detect a script and the whole value is that they trust the person's own voice.
Community
A community is a long commitment that pays late. Do not start one to hit a quarterly number.
It works when members get value from each other rather than only from you. That requires a reason to return that is not your product, visible norms, and consistent presence — a community that is quiet for a month does not recover easily. Seed it deliberately with people who will actually post; an empty room stays empty.
Measuring
Attribute honestly. Partnership traffic is often assisted rather than last-touch, so last-touch attribution will under-count it and you will kill something that was working. Agree the measurement method before launch, when neither side is defending a result.
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.
- 7d ago First seen · 57 lines · 59 tokens per session scan A 642ab97dd4ac
partnership-marketing is a skill published in the GitHub repository cbrock84/headcount (1,351 stars, last pushed 8d ago), licensed MIT. It adds 59 tokens to every session and 556 once invoked, about $0.0003 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…