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 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/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/presentation-design"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/presentation-design.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.00109 | $0.01014 |
| Opus 5.5 | $0.00044 | $0.00406 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 84 lines · 109 tokens per session scan A a9d95cfbf4ff
presentation-design is a skill published in the GitHub repository cbrock84/headcount (2,077 stars, last pushed 2d ago), licensed MIT. It adds 109 tokens to every session and 1,014 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
review
Visual Stack's primary tool. Build a UI wireframe and open it in an interactive review workspace where the user comments directly on the page, turning those comments into the next iteration — or point the same workspace at an app that is already running and review the real thing. Use when the user wants a wireframe…
phase-preview
Preview a signed-off design one release phase at a time — cut it down into a series of phase screens, each showing only what exists by that phase with the layout untouched, then put them on a scrubber you drag to watch the screen fill in release by release. Use when the user wants a Phase 1 / MVP version of an…
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.
wireframe
Alias for Visual Stack's review tool, which used to be called wireframe. Builds a UI wireframe and opens it in an interactive review workspace, or reviews an app that is already running. Use only when the user invokes /vstack:wireframe or $vstack:wireframe.
icon-composer-app-icon-workflow
Design, preview, validate, and integrate Apple app icons with Icon Composer. Use when a task mentions Icon Composer, .icon documents, Liquid Glass app icons, ictool preview exports, app icon design for iOS, iPadOS, macOS, or watchOS, or guided Icon Composer GUI work through Computer Use.
architecture-diagram
This skill should be used when a system design needs a diagram — "draw the architecture", "diagram this system", "show the components", "make an architecture/infrastructure/topology diagram", or visualizing boxes-and-arrows, data flow, regions, or failure paths for a design. It generates a self-contained dark-theme…