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 marketing-copywritinggit 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/marketing-copywriting)<a href="https://agentmods.dev/skills/cbrock84/headcount/marketing-copywriting"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/marketing-copywriting/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/marketing-copywriting"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/marketing-copywriting.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.00072 | $0.00577 |
| Opus 5 | $0.00036 | $0.00289 |
| Sonnet 5 | $0.00014 | $0.00115 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
marketing-copywriting 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing copywriting
Before writing a word
Settle four things. Copy written without them is decoration:
- Who is reading, and what they already believe.
- What one thing they should understand afterward.
- What they should do, singular.
- What is stopping them — the actual objection, not the polite version.
Writing
Lead with the consequence, not the mechanism. People buy what a thing lets them do. The feature is evidence for the claim, not the claim.
Specific beats superlative, always. "Cuts invoice processing from three days to twenty minutes" outperforms "dramatically faster" because it can be believed and checked. Every superlative is a claim your competitor also makes.
Write the way the reader talks. Their words, from research or support tickets, not internal vocabulary. If a phrase only exists inside the company, it does not go on the page.
One idea per section, in the reader's order — problem they recognize, why existing options fail, what you do differently, proof, what to do next. Not your org chart's order.
Every claim carries proof nearby: a number, a name, a screenshot, a quote. A page of unbacked claims reads as marketing and is discounted wholesale.
Editing
Edit in passes; doing them at once does none of them.
- Structure — is the order right, and is anything missing or duplicated? Fix this before sentences.
- Cut — remove every sentence that does not advance the argument. Then cut the first paragraph, which is usually warm-up.
- Sharpen — replace abstractions with specifics, passive with active, hedges with claims.
- Read aloud — anything you stumble over gets rewritten. This catches what silent reading does not.
Kill on sight
Empty openers ("In today's fast-paced world"), we-focused framing where you-focused works, hedges that weaken a true claim, feature lists with no consequence attached, and any adjective a competitor could equally use.
Never
- Write before you know what the reader should do next.
- Edit for elegance before the argument is right. Polished copy for the wrong claim is the more expensive mistake.
- Approve copy nobody read aloud. Rhythm problems are inaudible on the page.
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 First seen · 58 lines · 72 tokens per session scan A 0fac9e06728b
marketing-copywriting is a skill published in the GitHub repository cbrock84/headcount (1,351 stars, last pushed 8d ago), licensed MIT. It adds 72 tokens to every session and 577 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…