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 lead-capturegit 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/lead-capture)<a href="https://agentmods.dev/skills/cbrock84/headcount/lead-capture"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/lead-capture/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/lead-capture"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/lead-capture.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.00069 | $0.00692 |
| Opus 5.5 | $0.00028 | $0.00277 |
| Sonnet 5.5 | $0.00014 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
lead-capture 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 1mo 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead capture
What gating costs
Every gate trades reach for contacts. That trade is worth making only when the contact is genuinely worth more than the reader — which is true far less often than it is assumed.
Gate: things with immediate practical utility that a buyer would use during evaluation — templates, calculators, assessments, data. Do not gate: thought leadership, anything you want cited or shared, or anything a competitor publishes openly.
Lead magnets
The test is whether someone would pay a small amount for it. If not, it will not earn an email address that gets used.
The best ones are things people use rather than read: a template that saves an afternoon, a calculator that answers a specific question, a checklist for a process they are mid-way through. An ebook that restates blog posts is not one.
Match the magnet to a stage. Someone downloading a beginner's guide is not ready for a sales call, and treating them as if they are burns the list.
Free tools
The strongest form: durable, earns links, and qualifies by use rather than by claim.
Build one only if it does something genuinely useful standalone, and keep the gate light — let people use it, and ask for the email to save or export the result. Gating before value is delivered converts a fraction as well.
Popups and overlays
Popups work and are widely hated; both facts matter.
- Trigger on behavior, not time — exit intent, scroll depth, or a second visit. A popup at three seconds interrupts someone who has not yet decided whether to care.
- Once per visitor, remembered. Repeated interruption is what generates the hatred.
- Never on mobile mid-content. Beyond the user cost, it is penalized.
- Offer something specific. "Subscribe to our newsletter" is not an offer. "The pricing calculator" is.
- One clear dismissal. Hidden or tiny close buttons cost more in reputation than they gain in conversions.
Forms
Every field costs conversion. Ask for what you need to do the next step and nothing for a later one — enrichment can fill the rest. Explain any field whose purpose is not obvious, since unexplained fields are where people abandon.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +7 lines 337b61fe1ab5
- 1mo ago Changed · +7 lines 646da81651dc
- 1mo ago First seen · 55 lines · 69 tokens per session scan A e2044ccaeb85
lead-capture is a skill published in the GitHub repository cbrock84/headcount (2,069 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 692 once invoked, about $0.0003 per session on Opus 5.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
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
rotate-creative
Pause fatigued ads and ship fresh creative variants in their place. Works on both Meta and Google Ads. Use when CTR is dropping, frequency is climbing, or the user says "creative is tired" / "let's refresh ads". Always starts new variants paused.
launch-google-search
Launch a complete Google Ads Search campaign — campaign, ad group, responsive search ads, keywords, sitelinks, callouts, and negatives — built paused and ready to review. Use when the user wants to spin up a new Search campaign on Google Ads.
go
Compatibility entry for Visual Stack's former /vstack:go command. Runs the wireframe and UI review tool, now called review. Use only when the user invokes /vstack:go.
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.
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…