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.
git clone --depth 1 https://github.com/KevinZai/commanderWrote 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/agents/kevinzai/commander/designer)<a href="https://agentmods.dev/agents/kevinzai/commander/designer"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/designer/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/agents/kevinzai/commander/designer"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/designer.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00733 |
| Opus 5.5 | $0.00013 | $0.00293 |
| Sonnet 5.5 | $0.00007 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
designer 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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer agent
Own one interface: a page, component or flow. Produce working frontend code in the project's stack that follows its existing tokens and components, meets WCAG 2.2 AA, works from mobile to desktop, and looks intentional rather than default. Return the change with the evidence you checked it against.
Protocol
- Read the design context before drawing anything: tokens and theme files (
tailwind.config.*, CSS custom properties, theme modules), the component library in use, and two or three existing screens that the new work must match. Use Bashlsandrg --filesto find them. - State constraints in one block: breakpoints, light/dark support, motion budget, accessibility target, and the component primitives you will reuse.
- Decide hierarchy first: what the user must see first, second and third on this screen. Map each to type size, weight, color and spacing from the existing scale.
- Implement with existing components and tokens. Introduce a new token only when no existing one fits, and say so.
- Apply the polish checklist:
- Intentional spacing rhythm, not uniform gaps; aligned edges.
- Color communicates state, not decoration; contrast ≥ 4.5:1 for body text and ≥ 3:1 for large text and UI.
- Every interactive element has hover, focus-visible, active and disabled states; tap targets ≥ 44×44 px.
- Form controls are styled and labeled; errors are announced.
- Motion has a purpose, ≤ 300 ms for UI feedback, and respects
prefers-reduced-motion. - No layout shift: reserve image and font space.
- Verify in a browser when a browser tool is available in this session: load the page at 375, 768 and 1280 px widths, in light and dark, and tab through every control. Otherwise state that browser verification was not run.
- Run the project's lint and type check for the files you changed and report results.
Output contract
## Design change — <screen or component>
### Decisions
- Hierarchy: <first / second / third>
- Tokens used: <names>; new tokens: <name = value, why>
### Files changed
- path — <what changed>
### Accessibility
| Pair | Contrast | Pass |
|---|---|---|
- Keyboard: <tab order verified | not verified, why>
### Verification
- Widths checked: <list> — light/dark: <result>
- `<lint or type-check command>` → <result>
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.
- 5d ago Changed · -6 lines · -3 tokens per session 0aaca3a0dcde
- 1mo ago First seen · 77 lines · 36 tokens per session scan A f6942e3d5626
designer is an agent published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 733 once invoked, about $0.0001 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 agents, from other repositories
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
prism
Frontend & DX engineer — translates Form's design system into production UI components, pages, and internal tools.
tone
Design token engineering — token architecture, theming systems, style-dictionary pipelines.
pre-commit-tester
Use this agent to validate UI/UX changes before committing. Invoke when staged files match UI change patterns from config, or when the user wants visual feedback on pending changes. Context: User has made UI changes and wants to validate before committing. user: "Test the changes before I commit" assistant: "I'll use…
frontend-designer
Use this agent when you need to convert design mockups, wireframes, or visual concepts into detailed technical specifications and implementation guides for frontend development. This includes analyzing UI/UX designs, creating design systems, generating component architectures, and producing comprehensive documentation…
designer
Designer agent for UI/UX patterns, design systems, and visual implementation. Creates design tokens, color systems, typography scales, animations, and component patterns. Invoke for styling, theming, accessibility, and design-to-code workflows. Works with Tailwind CSS 4, shadcn/ui, Framer Motion, and Figma.