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 behavioral-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/behavioral-marketing)<a href="https://agentmods.dev/skills/cbrock84/headcount/behavioral-marketing"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/behavioral-marketing.svg" alt="Measured on agentmods" 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.00087 | $0.00947 |
| Opus 5 | $0.00044 | $0.00474 |
| Sonnet 5 | $0.00017 | $0.00189 |
| Haiku 4.5 | $0.00009 | $0.00095 |
Grade A, and why
behavioral-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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Behavioral marketing
People do not evaluate offers on merit and then act. They decide fast, under uncertainty, using whatever the context makes salient — and then explain the decision afterward. Marketing that assumes otherwise loses to marketing that does not.
The effects that most often explain a stuck conversion
Reference dependence. Nothing is judged absolutely. A price is high or low relative to whatever was shown first, so what you present first sets the frame for everything after it.
Loss aversion. Losing something registers considerably more than gaining the equivalent. This is why switching costs are underestimated by sellers and overestimated by buyers, and why "what you are currently losing" often outperforms "what you could gain."
Choice overload. More options reduce the likelihood of any choice being made. Beyond a small number, each additional option raises the cost of deciding faster than it raises the chance of a good match. If a pricing page has seven tiers, the problem is not the copy.
Status quo and default effects. Doing nothing is the most-chosen option in almost every context, and whatever is pre-selected is disproportionately taken. Whether a default exists is often a bigger lever than anything in the argument around it.
Social proof. Evidence of what similar others did carries more weight than claims about quality — and specificity matters. "Used by four hundred logistics teams" works where "trusted by thousands" does not, because the first is checkable and names a peer group.
Zero-price effect. Free is not a very low price; it is a different category that suspends cost-benefit reasoning. This makes free tiers powerful acquisition tools and dangerous pricing anchors.
Present bias. Immediate costs and benefits are weighted far above future ones. An annual plan competes against a monthly one on the immediacy of the charge, not on total value.
Goal-gradient and endowed progress. Effort increases as a visible goal approaches, and progress already granted counts. Progress indicators work; starting someone partway along works better.
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.
- 4d ago First seen · 78 lines · 87 tokens per session scan A 3cf94f1e4646
behavioral-marketing is a skill published in the GitHub repository cbrock84/headcount (1,320 stars, last pushed 5d ago), licensed MIT. It adds 87 tokens to every session and 947 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…