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/presentation-designnpx skills add cbrock84/headcount --skill presentation-designgit 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/presentation-design)<a href="https://agentmods.dev/skills/cbrock84/headcount/presentation-design"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/presentation-design.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 | $0.00109 | $0.01014 |
| Opus 5 | $0.00055 | $0.00507 |
| Sonnet 5 | $0.00022 | $0.00203 |
| Haiku 4.5 | $0.00011 | $0.00101 |
Grade A, and why
presentation-design 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation design
Decks
The deck is not the talk. Slides that contain the argument make the speaker redundant and the reader confused. Decide which artifact you are making — a spoken-support deck or a read-alone document — because they have opposite rules and the hybrid fails at both.
One idea per slide. If a slide needs a sub-argument, it is two slides. The cost of an extra slide is zero; the cost of a crowded one is that nothing on it lands.
Structure carries more than styling:
- Open with the change in the world that makes this matter now.
- State the problem in the audience's terms, not yours.
- The argument, in the smallest number of steps that hold.
- The evidence — one chart per claim, not a dashboard.
- The ask, stated explicitly. A deck that ends without an ask was a briefing.
On slides: headline states the takeaway, not the topic — "Churn concentrates in month two," not "Churn analysis." If the reader only reads headlines, they should get the argument.
Charts: one message each, labeled directly rather than through a legend, with the axis honest. Strip everything that is not carrying information.
Board decks and conference talks follow different rules
The structure above is shaped for persuasion to a room you are in. Two of the artifacts this skill is asked for are not that.
A board deck is read before the meeting, not presented at it. It goes out days ahead and is expected to be read, so it has to stand alone — which makes it the read-alone document, not the spoken-support deck.
- Separate what is for decision from what is for information, and say which is which on the page. A board meeting spent walking through updates is a board meeting with no decisions in it.
- Keep the format identical period over period. The value of a board pack is comparison across time, and a redesign destroys it. Same sections, same order, same metrics with the same definitions.
- Lead with what is not working. A pack that buries the problem on page nineteen costs credibility permanently once someone finds it, and they do.
- Bring the open question, not only the resolved one. A board shown finished thinking cannot help and eventually stops trying.
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 · 84 lines · 109 tokens per session scan A a9d95cfbf4ff
presentation-design is a skill published in the GitHub repository cbrock84/headcount (1,247 stars, last pushed 2d ago), licensed MIT. It adds 109 tokens to every session and 1,014 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-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…