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/listing-distributionnpx skills add cbrock84/headcount --skill listing-distributiongit 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/listing-distribution)<a href="https://agentmods.dev/skills/cbrock84/headcount/listing-distribution"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/listing-distribution.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.00062 | $0.00583 |
| Opus 5 | $0.00031 | $0.00292 |
| Sonnet 5 | $0.00012 | $0.00117 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
listing-distribution 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Listing distribution
Low effort, compounding, and consistently under-done. Also easy to do in a way that wastes weeks.
Choosing where to list
Judge each by whether real buyers use it, not by domain authority. The directories worth the time are the ones your buyers already consult during evaluation.
- Category review sites — highest value where they exist for your category. Buyers read these during active evaluation.
- Curated niche directories — moderate traffic, good qualification, usually a real editorial bar.
- Launch platforms — a spike, not a channel. Worth doing once, with preparation.
- Bulk submission lists — mostly worthless, and the low-quality end carries real risk. Skip them.
Preparing once, reusing everywhere
Assemble a kit before submitting anywhere: descriptions at several lengths, logo and screenshots at the common sizes, category selections, feature list, pricing summary, and the founder or company details these forms always want. Submissions then take minutes instead of an afternoon each.
Keep the positioning identical across listings. Inconsistent descriptions across directories are both a brand problem and a signal problem.
Review platforms
The listings that most influence buyers. Claim the profile, complete it fully, and keep it current — a stale listing with old pricing costs deals.
Ask for reviews from customers at a success moment, never with an incentive tied to sentiment. Respond to every negative review specifically and without defensiveness; prospects read the responses more carefully than the reviews.
Comparison and alternative pages
Pages targeting "X versus Y" and "alternatives to X" capture buyers already in evaluation, which is the highest-intent traffic available.
Write them honestly. Name where the competitor is genuinely better — a comparison that finds you superior on every axis is not believed, and buyers checking it against their own experience will discount the whole page. Keep them current; a comparison against a competitor's two-year-old feature set is worse than nothing.
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 Changed · +6 lines 392a1fdb710b
- 6d ago First seen · 55 lines · 62 tokens per session scan A a59d55b2b0b4
listing-distribution is a skill published in the GitHub repository cbrock84/headcount (1,247 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 583 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-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…