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 agentmods add skills/cbrock84/headcount/public-relationsnpx skills add cbrock84/headcount --skill public-relationsgit 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/public-relations)<a href="https://agentmods.dev/skills/cbrock84/headcount/public-relations"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/public-relations.svg" alt="Measured on agentmods" height="20"></a>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.00065 | $0.00738 |
| Opus 5 | $0.00032 | $0.00369 |
| Sonnet 5 | $0.00013 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
public-relations 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 yesterday.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Public relations
Newsworthy is a high bar
Most company news is not news. Before pitching, find the actual story — the thing a journalist's readers would care about with your company removed from the sentence.
Genuinely newsworthy: a first, a significant number, a counter-intuitive finding from data you uniquely have, a named conflict, a consequential person moving. Not newsworthy: a funding round of ordinary size, a feature release, a partnership, an award, a rebrand.
If there is no story, the answer is to build one — original research is the most reliable way — not to pitch harder.
Pitching
Journalists receive hundreds of pitches a day and reject most in seconds.
- Pitch a person, not an outlet. Read three of their recent pieces first and reference one specifically and accurately. Generic personalization is worse than none.
- Subject line is the pitch. If it does not carry the story, nothing else will be read.
- Three sentences: the story, why now, why you can speak to it. Offer the assets — data, interview, images — rather than attaching them.
- No embargo without agreement. Declaring one unilaterally is not binding and reads as presumptuous.
- One follow-up, then stop.
Interviews
Decide the two or three things you want to have said, and find honest routes back to them. Never speculate, never say anything you would not want printed, and treat nothing as off the record unless explicitly agreed in advance — and even then, assume it may not hold.
"I don't know, I'll find out" is a complete and respectable answer.
When a story goes badly
- Speed matters, but accuracy matters more. A fast wrong statement extends the story.
- Say what happened, what you are doing, and when you will update. Only that.
- Never dispute a factual detail you have not verified, and never attack the reporter. Both guarantee a second story.
- Correct genuine errors privately, with evidence, and specifically. Vague complaints about tone achieve nothing.
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.
- yesterday First seen · 68 lines · 65 tokens per session scan A c72e43a68bc0
public-relations is a skill published in the GitHub repository cbrock84/headcount (1,247 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 738 once invoked, about $0.0003 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.
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.
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.
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…