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 landing-page-cro-expertgit 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/landing-page-cro-expert)<a href="https://agentmods.dev/skills/cbrock84/headcount/landing-page-cro-expert"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/landing-page-cro-expert/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/landing-page-cro-expert"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/landing-page-cro-expert.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.00090 | $0.00889 |
| Opus 5 | $0.00045 | $0.00445 |
| Sonnet 5 | $0.00018 | $0.00178 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
landing-page-cro-expert 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 7d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing page CRO
Diagnose before rewriting
A page converts when a visitor understands what this is, believes it will work for them, and has no unresolved objection at the moment they are asked to act. Failures are almost always one of those three, and the remedy differs entirely.
Read the page as a stranger who has five seconds. Then answer:
- What is this, in the reader's words? If the hero requires domain knowledge to parse, nothing below it matters.
- Who is it for? A page for everyone converts nobody. Specificity is a conversion tactic, not a marketing luxury.
- Why this instead of the alternative — including doing nothing, which is the real competitor.
- What is the single action? Multiple competing calls to action reliably reduce all of them.
The hero
Most of the outcome, decided in the space of a phone screen.
- Headline states the outcome, not the category and not a slogan. "Close your books in two days, not two weeks" beats "Modern accounting infrastructure."
- Subhead handles the obvious next question — usually how, or for whom.
- One primary call to action, above the fold, with a label describing what happens next rather than "Submit" or "Get started."
- Proof in the first screen. A logo row, a number, a named customer. Claims made with no evidence in sight are discounted wholesale.
- Show the product. A screenshot of the real thing outperforms an abstract illustration for almost every software product.
Down the page
Order by the reader's questions, not by your feature list: what it does → why it is better than what they do now → proof → objections → price → act.
Every claim needs evidence near it. Every section should be removable — if cutting it changes nothing, cut it. Long pages are fine; padded pages are not.
Repeat the call to action at each natural decision point, always the same action.
Objections
List the real reasons people do not buy — cost, switching effort, trust, whether it works for their case, who else uses it — and answer each on the page. Objections not handled on the page are handled by leaving.
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.
- 7d ago Changed · +6 lines f5851156bd84
- 11d ago First seen · 78 lines · 90 tokens per session scan A 71fd8aa3b53e
landing-page-cro-expert is a skill published in the GitHub repository cbrock84/headcount (1,351 stars, last pushed 8d ago), licensed MIT. It adds 90 tokens to every session and 889 once invoked, about $0.0005 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.
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.