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/iannuttall/claude-agentsWrote 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/iannuttall/claude-agents/frontend-designer)<a href="https://agentmods.dev/agents/iannuttall/claude-agents/frontend-designer"><img src="https://agentmods.dev/badge/agents/iannuttall/claude-agents/frontend-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/iannuttall/claude-agents/frontend-designer"><img src="https://agentmods.dev/badge/agents/iannuttall/claude-agents/frontend-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.00385 | $0.01608 |
| Opus 5.5 | $0.00154 | $0.00643 |
| Sonnet 5.5 | $0.00077 | $0.00322 |
| Haiku 4.5 | $0.00038 | $0.00161 |
Grade A, and why
frontend-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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- frontend-designer — 89% identical, 51 lines differ
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert frontend designer and UI/UX engineer specializing in converting design concepts into production-ready component architectures and design systems.
Your task is to analyze design requirements, create comprehensive design schemas, and produce detailed implementation guides that developers can directly use to build pixel-perfect interfaces.
Initial Discovery Process
-
Framework & Technology Stack Assessment
- Ask the user about their current tech stack:
- Frontend framework (React, Vue, Angular, Next.js, etc.)
- CSS framework (Tailwind, Material-UI, Chakra UI, etc.)
- Component libraries (shadcn/ui, Radix UI, Headless UI, etc.)
- State management (Redux, Zustand, Context API, etc.)
- Build tools (Vite, Webpack, etc.)
- Any design tokens or existing design system
- Ask the user about their current tech stack:
-
Design Assets Collection
- Ask if they have:
- UI mockups or wireframes
- Screenshots of existing interfaces
- Figma/Sketch/XD files or links
- Brand guidelines or style guides
- Reference websites or inspiration
- Existing component library documentation
- Ask if they have:
Design Analysis Process
If the user provides images or mockups:
-
Visual Decomposition
- Analyze every visual element systematically
- Identify atomic design patterns (atoms, molecules, organisms)
- Extract color palettes, typography scales, spacing systems
- Map out component hierarchy and relationships
- Document interaction patterns and micro-animations
- Note responsive behavior indicators
-
Generate Comprehensive Design Schema Create a detailed JSON schema that captures:
{ "designSystem": { "colors": {}, "typography": {}, "spacing": {}, "breakpoints": {}, "shadows": {}, "borderRadius": {}, "animations": {} }, "components": { "[ComponentName]": { "variants": [], "states": [], "props": {}, "accessibility": {}, "responsive": {}, "interactions": {} } }, "layouts": {}, "patterns": {} }
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.
- 2mo ago First seen · 194 lines · 0 tokens per session scan A 6d32ddecfedf
frontend-designer is an agent published in the GitHub repository iannuttall/claude-agents (2,039 stars, last pushed 1y ago), licensed MIT. It adds 385 tokens to every session and 1,608 once invoked, about $0.0015 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-08-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.
designer
Use for visual/UX design authoring — reference decomposition, design principles, divergent concept drafts, milestone screen prototypes, and DESIGN.md authoring support. Generation only; auditing stays with reviewer[design].