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 commands/sukirman1901/frontend-expert/designgit clone --depth 1 https://github.com/sukirman1901/frontend-expertWrote 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/commands/sukirman1901/frontend-expert/design)<a href="https://agentmods.dev/commands/sukirman1901/frontend-expert/design"><img src="https://agentmods.dev/badge/commands/sukirman1901/frontend-expert/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.1 | $0.00024 | $0.00545 |
| Opus 5 | $0.00012 | $0.00272 |
| Sonnet 5 | $0.00005 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
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 6d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invoke the design-reviewer agent.
Skills to load (in order)
anti-ai-slopui-feeldesign-tokens(when a token file is available)responsive-ui— all-devices / breakpoint adherenceaccessibilityweb-performanceui-componentsas needed for pattern/state checksmotion— when animated / marketing motion (family budget frommotion-families.md; hand-roll)design-fidelity— when Figma/mock/screenshot is in scopefe-devtools— when measuring (Lighthouse/axe); never fabricate scoresmarketing-landing— when auditing marketing / landing pagesfrontend-judgmentwhen recommending redesign directionsfrontend-testing— note coverage gaps as Info only
Modes
/designor/audit— full audit (default)/design --quick— major issues only/design --token <file>— audit against a specific token preset/design --component <name>— audit one component
$ARGUMENTS selects the mode and options.
What to do
- Detect the project's framework / design system before recommending patterns
- Scan for AI aesthetic anti-patterns (incl. decorative motion spam / hero-only landing)
- Check ui-feel craft details
- Check token adherence when a token file is available
- Check responsive (320/768/1024/1440) + full-width CTA <768 — High if greenfield layout skips it
- Check shell chrome on dashboards (theme topbar, avatar menu, custom selects)
- Check marketing landing section stack when applicable (not hero-only; hand-roll)
- Check hierarchy + typography ladder when DOM/screenshots available
- Check motion family budget + reduced-motion when animation present
- Review accessibility against WCAG 2.1 AA
- Note performance risks relevant to UI (LCP/INP/CLS); use
fe-devtoolswhen measuring - Output the design-reviewer scorecard (incl. Typography + Responsive + Motion + Landing) — mark unevaluated fields explicitly
- End with prioritized next moves (max 5)
Do not fabricate visual hierarchy or contrast scores without screenshots or token data.
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.
- 6d ago First seen · 49 lines · 24 tokens per session scan A 8b5e2300e5cc
design is a command published in the GitHub repository sukirman1901/frontend-expert (10 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 545 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
ux-recommend
The v2 flagship. Runs the 5-parallel-search Python engine across 11 data manifests (75+ styles, 170+ palettes, 65+ type pairs, 120+ components, 170+ industries, 110+ UX laws, 50+ motion presets, 120+ anti-patterns, 92 brand specs) and returns a complete recommended design system for your project — with always-on…
review-css-complexity
Scan codebase for overly complex CSS/styling patterns that should be simplified.
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.
revisar-ui
Auditoria visual retroativa de 6 pilares do código frontend implementado.