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/interface-redesignnpx skills add cbrock84/headcount --skill interface-redesigngit 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/interface-redesign)<a href="https://agentmods.dev/skills/cbrock84/headcount/interface-redesign"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/interface-redesign.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.00077 | $0.00603 |
| Opus 5 | $0.00039 | $0.00302 |
| Sonnet 5 | $0.00015 | $0.00121 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
interface-redesign 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interface redesign
Most interfaces do not need rebuilding. They need a dozen specific things fixed, in the right order.
Audit first
Go through the real product, on a real device, doing a real task. Record what you find in these categories — the order is the priority order:
- Structural — unclear primary action, competing focal points, navigation that does not match the mental model. These are the only ones worth a rebuild.
- Systemic — inconsistent spacing, more type sizes than a scale would allow, palette drift, components that exist in variants. High impact, mechanical to fix.
- Craft — weak hierarchy, poor contrast, unfinished states, cramped density.
- Cosmetic — dated shadows, default border radii, stock illustration.
The generic-AI-product tells
These are the specific things that make a product read as unconsidered. They are worth naming because they are all cheap to fix:
- Default framework styling left in place — the untouched button, the starter-template card.
- One accent color used for every emphasis, so nothing is emphasized.
- Uniform spacing everywhere, so nothing groups.
- Centered everything, including body copy.
- Emoji standing in for iconography.
- Gradients on surfaces that carry no meaning.
- Empty and error states that were never designed.
Sequencing
Fix in this order, because each makes the next easier to see:
- Tokens — spacing scale, type scale, palette. This alone resolves most systemic findings.
- Hierarchy on the two or three highest-traffic screens.
- States: empty, loading, error, overflow.
- Component consolidation.
- Cosmetic pass.
Restyle or rebuild
Rebuild only when the structure is wrong — when the information architecture does not match how people work. Everything else is a restyle, and a restyle that ships beats a rebuild that stalls.
Never
- Restyle a screen whose problem is structural. New paint on a broken flow buys nothing.
- Change navigation and visual language in the same release. When something breaks you will not know which one did it.
- Remove a path because it looks unused without checking who uses it and what they do next.
- Ship a redesign with no way back. Keep the old path reachable until the new one is proven.
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 · 61 lines · 77 tokens per session scan A d9d3dfb5be79
interface-redesign is a skill published in the GitHub repository cbrock84/headcount (1,247 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 603 once invoked, about $0.0004 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
swiftui-liquid-glass
Design, implement, review, and validate SwiftUI Liquid Glass interfaces across iOS and macOS. Use when choosing native glass effects, grouped glass surfaces, glass button styles, morphing transitions, availability fallbacks, or removing conflicting custom chrome.
shiny-bslib
Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…
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.
frontend-design
Guidance for distinctive, intentional frontend/UI design — aesthetic direction, typography, layout, motion, and copy — when building new UI or reshaping existing UI. Gates by scope before designing: a light/surgical change (one component, one page section, extending an existing design system) gets inline design…
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.