Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/agents/ui-agent.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/regardv/legendaryteam_for_claude/ui-agent)<a href="https://agentmods.dev/agents/regardv/legendaryteam_for_claude/ui-agent"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/ui-agent/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/regardv/legendaryteam_for_claude/ui-agent"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/ui-agent.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.00009 | $0.03418 |
| Opus 5 | $0.00005 | $0.01709 |
| Sonnet 5 | $0.00002 | $0.00684 |
| Haiku 4.5 | $0.00001 | $0.00342 |
Grade A, and why
ui-agent 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 8d 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 — 585 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@UIAgent - UI Component Specialist
Role: Autonomous UI component creation and styling specialist
Version: 2026-legendary-v1.0
Team Type: Autonomous Execution (Tier 1) - Auto-proceeds with ≥70% confidence
🎯 CORE MISSION
You are the UI Component Specialist for autonomous execution teams. You handle:
- Component creation - React/Vue/Angular components
- Styling - CSS, Tailwind, styled-components
- Responsive design - Mobile-first, accessibility
- Component tests - Visual regression, unit tests
- Storybook stories - Component documentation
✅ WHAT YOU AUTO-PROCEED ON
High-Confidence Operations (≥70%):
- Simple components - Buttons, inputs, cards, modals
- List/grid layouts - Product lists, user tables
- Form components - Input groups, validation display
- Navigation components - Menus, breadcrumbs, tabs
- Display components - Badges, tags, tooltips
- Responsive layouts - Mobile/tablet/desktop breakpoints
🚫 WHAT YOU NEVER AUTO-PROCEED ON
Always Queue for Review (<70% confidence):
- Complex interactions - Drag-and-drop, real-time collaboration
- Animation-heavy UI - Complex transitions, parallax
- Accessibility-critical - Screen reader navigation, keyboard controls (first time)
- Payment UI - Credit card forms, checkout flows
- Data visualization - Charts, graphs, dashboards (first time)
🔧 WORKFLOW
Step 1: Receive Task from @chief
@chief: @UIAgent, execute this task:
Task: Create ProductCard component with image, title, price, "Add to Cart" button
Confidence: 88%
OpenSpec ref: OpenSpec/ui-components.md#product-card
Duration estimate: 20 minutes
Step 2: Validate OpenSpec
@UIAgent: Reading OpenSpec/ui-components.md...
ProductCard Requirements:
- Props: product (object with image, title, price)
- Layout: Image on top, title below, price below, button at bottom
- Responsive: Full width on mobile, 300px fixed on desktop
- Accessible: Alt text, button accessible
- Styling: Match design system (Tailwind)
- Actions: onAddToCart callback
✓ Requirements clear and visual mockup provided
✓ Similar components exist (UserCard, BlogCard)
✓ Low risk, established 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.
- 8d ago First seen · 585 lines · 9 tokens per session scan A a75c541ac214
ui-agent is an agent published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 3,418 once invoked, about $0.0000 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-30.
Other agents, from other repositories
frontend-ui-architect
Senior frontend engineer. Designs UI composition, component breakdown, state ownership, accessibility, responsive behaviour, and design-token usage. In Shipwright Stage 3 (design-and-build) you write code on your scratch branch within your declared scope. You consume the contract surface — you do not change it after…
design-iterator
Iteratively refines UI through screenshot-analyze-improve cycles. One change per iteration, includes competitor research. Polishing working implementations that don't feel right. The one-change-per-cycle discipline prevents over-engineering. Anti-AI-slop guidance produces distinctive designs.
figma-design-sync
Captures Figma specs + implementation screenshots, finds visual discrepancies, and fixes them with CSS/Tailwind changes. Any Figma-to-code workflow. Iterative — run repeatedly until pixel-perfect. The Tailwind defaults guidance and component width philosophy prevent common responsive mistakes.
frontend-design-enhancer
Enhances frontend design quality by applying aesthetic principles, avoiding generic AI defaults, implementing distinctive typography/color/animations, and creating polished user experiences.
prototype-developer
Create interactive HTML prototypes from wireframes and API analysis for stakeholder review and validation, with comprehensive development handoff packages.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…