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 visual-contentgit 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/visual-content)<a href="https://agentmods.dev/skills/cbrock84/headcount/visual-content"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/visual-content/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/visual-content"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/visual-content.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.00670 |
| Opus 5.5 | $0.00029 | $0.00268 |
| Sonnet 5.5 | $0.00014 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
visual-content 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual content
The format follows the content's shape
- Sequence or process → carousel. One step per slide, one idea per slide.
- Comparison or relationship → single diagram. A carousel would break what needs to be seen at once.
- A single memorable claim → quote graphic.
- Quantity, trend, or proportion → chart, with one message.
- Anything with more than about seven elements → it is two visuals.
Choosing format by what is fashionable rather than by the content's shape is why so many carousels are a paragraph cut into ten pieces.
Carousels
The first slide is the entire hook — treat it as a headline, not a title card. Every subsequent slide must earn the swipe, which means each ends slightly incomplete.
Consistent template across slides: same margins, same type positions, same palette. Variation across slides reads as error. Number them so the reader knows the commitment.
Last slide lands the idea. A last slide that only says "follow for more" wastes the only slide with guaranteed attention from everyone who finished.
Infographics and diagrams
A diagram earns its place when it shows a relationship prose would take three paragraphs to establish. If it restates the text, cut it.
Label directly on the element. Legends make the reader hold a mapping in memory while looking elsewhere. Strip anything not carrying meaning — decorative gradients, 3D effects, and drop shadows on data.
Designing for the actual context
Almost all of this is seen small, on a phone, in a feed, at speed. Test at that size before finishing. If the headline is not readable at thumbnail scale, it does not exist.
High contrast between subject and background is what stops the scroll. Subtlety is a desktop luxury.
Where images are generated
Write the prompt as a brief: subject, composition, lighting, palette, mood, and negative constraints. Generate one concept per image. Then check the output actually renders any embedded text correctly and matches the brand palette — generated imagery drifts, and drifted brand color is worse than no brand color.
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 25aa130e7915
- 1mo ago First seen · 59 lines · 72 tokens per session scan A 0aa4f6c762f7
visual-content is a skill published in the GitHub repository cbrock84/headcount (2,077 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session and 670 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-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…