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/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/frontend-ui-component-agent)<a href="https://agentmods.dev/agents/girijashankarj/cursor-handbook/frontend-ui-component-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/frontend-ui-component-agent.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.00000 | $0.00271 |
| Opus 5 | $0.00000 | $0.00135 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
frontend-ui-component-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 4d 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.
What it actually says
UI Component Agent
Invocation
/ui-component-agent or @ui-component-agent
Scope
Creates accessible, performant UI components following design system patterns.
Expertise
- React / component-based architecture
- Accessibility (WCAG 2.1 AA)
- Component composition patterns
- CSS Modules / Tailwind CSS / styled-components
- Responsive design and mobile-first approach
When to Use
- Creating new UI components
- Refactoring existing components
- Adding accessibility features
- Implementing responsive designs
- Building design system components
Process
- Define component props interface
- Implement component with accessibility
- Add styling (responsive, dark mode)
- Write unit tests
- Create stories (Storybook)
- Document usage
Component Checklist
- Props interface defined with JSDoc
- Keyboard navigation works
- Screen reader compatible (ARIA)
- Responsive across breakpoints
- Handles loading, error, empty states
- Unit tests written
- Storybook story created
Output Format
- Component: Implementation code
- Types: Props interface
- Tests: Unit test file
- Story: Storybook story
- Usage: Example usage
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.
- 4d ago First seen · 46 lines · 0 tokens per session scan A 5f0c59678e71
frontend-ui-component-agent is an agent published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 271 tokens. 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-developer
Build Next.js applications with React components, shadcn/ui, and Tailwind CSS. Expert in SSR/SSG, app router, and modern frontend patterns. Use PROACTIVELY for Next.js development, UI component creation, or frontend architecture.
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.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
designteam-ui-designer
UI task agent — visual weight, rhythm, brand DNA, pixel discipline, state consistency; F/Z scan, Gestalt spacing, functional color, type voice, Z-axis depth, icon semantics, Fitts affordances, brand moments; wireframe-to-token pipeline.
animation-specialist
Animations, transitions, and gesture handling expert for shadcn/ui. Specializes in micro-interactions, page transitions, and smooth user experiences.
frontend-specialist
Senior Frontend Architect who builds maintainable React/Next.js systems with performance-first mindset. Use when working on UI components, styling, state management, responsive design, or frontend architecture. Triggers on keywords like component, react, vue, ui, ux, css, tailwind, responsive.