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/sales-enablementnpx skills add cbrock84/headcount --skill sales-enablementgit 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/sales-enablement)<a href="https://agentmods.dev/skills/cbrock84/headcount/sales-enablement"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/sales-enablement.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.00068 | $0.00590 |
| Opus 5 | $0.00034 | $0.00295 |
| Sonnet 5 | $0.00014 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
sales-enablement 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales enablement
Collateral gets used when it solves a problem the seller has in a live conversation. Everything else is filed and forgotten.
Know where deals actually stall
Before making anything, find where deals die: first call, after the demo, at pricing, at security review, at the champion's boss. Each stall has a different remedy, and building for the wrong one produces beautifully designed collateral nobody opens.
The core set
Pitch deck — a structure, not a script. Problem the buyer recognizes, why current approaches fail, what you do differently, proof, commercials, next step. Ten to fifteen slides, each with a takeaway headline.
One-pager — what the champion forwards internally to people you will never meet. It must survive being read with no context and no presenter. This is usually the highest-leverage asset and the most neglected.
Objection handling — the real objections, in the words prospects use, with responses that acknowledge the legitimate part first. A response that denies the objection reads as evasion and ends trust.
Battlecards — per competitor: where they genuinely win, where you do, the traps to avoid, and what to say when the prospect raises them. Cards claiming you win everywhere get ignored by sellers, who know better.
Case studies — situation, what changed, measurable result, in the buyer's language. One verifiable number beats a page of adjectives.
Demo
Demo the outcome, not the interface. Start where the value is visible, not at login and settings.
Tailor to the problem they told you about — a feature tour of everything demonstrates that you were not listening. Prepare for the three things that always go wrong, and know how to reach the value moment inside five minutes when time gets cut.
Maintaining
Collateral rots. Every asset needs an owner and a review date, and anything referencing pricing, competitors, or product capability needs checking every quarter. A battlecard describing a competitor's old product loses deals.
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 · 58 lines · 68 tokens per session scan A 95ded8dfd365
sales-enablement is a skill published in the GitHub repository cbrock84/headcount (1,284 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 590 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…