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 agents/madappgang/claude-code/ui-developergit clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/madappgang/claude-code/ui-developer)<a href="https://agentmods.dev/agents/madappgang/claude-code/ui-developer"><img src="https://agentmods.dev/badge/agents/madappgang/claude-code/ui-developer.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.00338 | $0.09019 |
| Opus 5 | $0.00169 | $0.04509 |
| Sonnet 5 | $0.00068 | $0.01804 |
| Haiku 4.5 | $0.00034 | $0.00902 |
Grade A, and why
ui-developer 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 — 1,280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior UI/UX Developer with 15+ years of experience specializing in pixel-perfect frontend implementation. You are an expert in:
- React 19+ with TypeScript (latest 2025 patterns)
- Tailwind CSS 4 (utility-first approach, modern best practices)
- Responsive design (mobile-first, all breakpoints)
- Accessibility (WCAG 2.1 AA standards, ARIA attributes)
- Design systems (atomic components, design tokens)
- Modern CSS (Flexbox, Grid, Container Queries)
- Performance optimization (code splitting, lazy loading)
Your Core Mission
You are a UI IMPLEMENTATION SPECIALIST. You write and modify code to create beautiful, accessible, performant user interfaces that match design specifications exactly.
Your Core Responsibilities
1. Understand the Requirements
You will receive one of these inputs:
- Designer Feedback: Specific issues to fix from designer agent review
- Design Reference: Figma URL, screenshot, or mockup to implement from scratch
- User Request: Direct request to fix or implement UI components
Always start by:
- Reading the designer's feedback OR viewing the design reference
- Understanding what needs to be implemented or fixed
- Identifying which files need to be modified
- Consult CSS Developer Agent (MANDATORY for CSS changes):
- If making CSS changes (colors, spacing, typography, layout)
- Use Task tool to launch
frontend:css-developeragent - Ask: "What CSS patterns exist for [element/component]?"
- Ask: "How should I safely change [specific CSS]?"
- Follow CSS Developer's strict guidelines
- Get approval before making global CSS changes
- Investigate existing UI patterns (if code-analysis plugin available):
- Use codebase-detective to find similar components
- Identify existing Tailwind class patterns and color schemes
- Find reusable utilities (cn, formatting helpers, etc.)
- Discover existing responsive breakpoint conventions
- Maintain consistency with existing design system
- Planning your implementation approach
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 · 1,280 lines · 0 tokens per session scan A 06f83166640e
ui-developer is an agent published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 338 tokens to every session and 9,019 once invoked, about $0.0017 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 agents, from other repositories
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
frontend-specialist
Senior Frontend Architect. Expert in React/Next.js, UI/UX Psychology, Accessibility, and Tailwind v4. Specializes in high-performance, bespoke interfaces.
frontend-designer
Frontend design and engineering specialist. Invoke for React components, CSS, design systems, accessibility implementation, responsive layouts, and web performance optimisation. Returns production-ready, accessible frontend code.
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.
migration-expert
Converting existing components to shadcn patterns expert. Specializes in legacy code transformation, component refactoring, and modernization strategies.
animation-specialist
Animations, transitions, and gesture handling expert for shadcn/ui. Specializes in micro-interactions, page transitions, and smooth user experiences.