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 positioning-and-messaginggit 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/positioning-and-messaging)<a href="https://agentmods.dev/skills/cbrock84/headcount/positioning-and-messaging"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/positioning-and-messaging.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.00081 | $0.00490 |
| Opus 5 | $0.00041 | $0.00245 |
| Sonnet 5 | $0.00016 | $0.00098 |
| Haiku 4.5 | $0.00008 | $0.00049 |
Grade A, and why
positioning-and-messaging 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 3d 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.
What it actually says
Positioning and messaging
Positioning is upstream of everything. A campaign built on unsettled positioning optimizes the wrong sentence.
The five decisions
- Competitive alternative — what the buyer does today if you do not exist. Often a spreadsheet or an intern, not a competitor.
- Unique attributes — what you have that the alternative does not. Features, factual.
- Value — what those attributes let the customer do that they could not before. Not the feature; the consequence.
- Who cares most — the segment for whom that value is urgent rather than pleasant. Narrower than comfortable.
- Market frame — the category you ask to be judged in. This sets every expectation the buyer brings, including on price.
Get these in order. Most positioning failures are step 5 done first: picking an exciting category and reverse-engineering the value.
Messaging that inherits from it
- One-liner — what it is, for whom, instead of what. No adjectives that a competitor could not also claim.
- Three pillars — the value claims, each with proof attached. A claim with no evidence is a slogan.
- Objection handling — the four things prospects actually push back on, answered plainly.
- Words to avoid — including the category terms that would frame you wrongly.
Testing it
Read the one-liner to someone in the target segment and ask what they think it does and who it is for. If they answer with your category but the wrong use case, the frame is wrong. If they answer with a competitor's name, the differentiation is not landing.
Never
- Position against a competitor the buyer has not heard of.
- Widen the segment because the narrow one feels small. Diffuse positioning converts nobody.
- Change the one-liner per channel. Channels change format, not meaning.
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.
- 3d ago First seen · 46 lines · 81 tokens per session scan A f7892756fb9e
positioning-and-messaging is a skill published in the GitHub repository cbrock84/headcount (1,284 stars, last pushed 3d ago), licensed MIT. It adds 81 tokens to every session and 490 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-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…