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 seo-strategygit 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/seo-strategy)<a href="https://agentmods.dev/skills/cbrock84/headcount/seo-strategy"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/seo-strategy/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/seo-strategy"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/seo-strategy.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.00074 | $0.01083 |
| Opus 5.5 | $0.00030 | $0.00433 |
| Sonnet 5.5 | $0.00015 | $0.00217 |
| Haiku 4.5 | $0.00007 | $0.00108 |
Grade A, and why
seo-strategy 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO strategy
Diagnose in this order
Skipping to content when the problem is technical wastes months. Work down; stop when you find the break.
- Can it be crawled? Robots directives, noindex left on after a launch, blocked resources, crawl budget wasted on parameter and filter URLs.
- Can it be indexed? Check what is actually in the index versus what should be. Canonicals pointing at the wrong page and unintended duplicates are the two usual causes.
- Does the page deserve to rank? Search intent match first. A page can be technically perfect and still lose because it answers a different question than the query asks.
- Does the site have the authority to rank for it? Some terms are out of reach for now. Targeting them is a decision to spend without return.
Architecture
Structure follows how people look for things, not how the company is organized.
- Anything important reachable within three clicks of the home page.
- Group related pages so internal linking is natural, not retrofitted.
- One URL per thing. Parameters, trailing-slash variants, and case differences that all resolve are duplicate content in the crawler's eyes.
- URLs readable and stable. Changing them costs equity even done correctly.
Internal linking is the most underused lever available: it is fully within your control, and it directs authority to the pages you actually care about. Link with descriptive anchor text from your strongest pages to the ones that need help.
Performance and mobile
Speed and mobile usability are ranking inputs and, more importantly, conversion inputs. Audit them as part of every SEO review rather than treating them as an engineering concern.
Measure on field data from real users where available, not only lab tools. Lab scores on a fast connection routinely miss what mobile users experience.
The three that matter:
- Loading — how long until the largest visible element renders. Usually fixed by image sizing and format, render-blocking resources, and slow server response.
- Interaction responsiveness — how long the page takes to react to a tap or click. Usually fixed by reducing main-thread JavaScript work.
- Layout stability — how much content shifts while loading. Almost always fixed by reserving space for images, ads, and embeds before they load.
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 1f155cdf20b7
- 1mo ago Changed · +6 lines 0cd73c7b6096
- 1mo ago First seen · 90 lines · 74 tokens per session scan A 208fc2927abb
seo-strategy is a skill published in the GitHub repository cbrock84/headcount (2,089 stars, last pushed 8d ago), licensed MIT. It adds 74 tokens to every session and 1,083 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…