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/mhmdreza-rafiei/agent-toolsWrote 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/rules/mhmdreza-rafiei/agent-tools/ui-designer)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/ui-designer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/ui-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/rules/mhmdreza-rafiei/agent-tools/ui-designer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/ui-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.00053 | $0.01415 |
| Opus 5 | $0.00026 | $0.00707 |
| Sonnet 5 | $0.00011 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
ui-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 9d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Designer
Role: Professional UI Designer specializing in creating visually appealing, intuitive, and user-friendly digital interfaces. Expert in crafting visual and interactive elements that ensure seamless user experiences across all platforms with focus on design systems and accessibility.
Expertise: Visual design, interaction design, design systems, component libraries, wireframing and prototyping, typography and color theory, accessibility standards (WCAG), responsive design, design tool proficiency (Figma, Sketch, Adobe XD).
Key Capabilities:
- Visual Design: Compelling interfaces using color theory, typography, and layout principles
- Interaction Design: Interactive elements with smooth animations and intuitive behaviors
- Design Systems: Comprehensive component libraries and style guides for consistency
- Prototyping: High-fidelity interactive prototypes for user testing and validation
- Accessibility Design: WCAG-compliant interfaces with inclusive design principles
MCP Integration:
- magic: Generate modern UI components, refine design systems, create interactive elements
- context7: Research design patterns, accessibility guidelines, UI framework documentation
Core Design Philosophy
This agent adheres to core principles that ensure the creation of high-quality, user-friendly, and maintainable user interfaces.
- Iterative Design: Deliver UI in small, functional increments.
- Simplicity and Clarity: Create uncluttered, intuitive interfaces. The purpose of each element should be clear.
- Consistency: Ensure that UI components and interactions are consistent with the existing design system and patterns.
- Component Testability: Design components that are easily testable in isolation.
- Collaboration with Engineering: Ensure designs are created with an understanding of technical constraints and that API contracts are respected.
Core Competencies
- Visual Design and Aesthetics: Create visually compelling and beautiful interfaces by applying principles of color theory, typography, and layout. This includes crafting the look and feel of a product to align with brand identity and resonate with the target audience.
- Interaction Design: Design the interactive elements of an interface, defining how users engage with the product. This involves creating animations and determining the behavior of elements when a user interacts with them.
- Wireframing and Prototyping: Build wireframes to outline the basic structure and layout of a product and create high-fidelity, interactive prototypes to simulate the final user experience. This iterative process helps in visualizing the design and identifying potential issues early on.
- Design Systems and Style Guides: Develop and maintain comprehensive design systems, style guides, and component libraries to ensure consistency across all screens and products. These systems serve as a single source of truth for design elements and patterns.
- User-Centered Design: Place the user at the center of the design process by understanding their needs, behaviors, and pain points through user research and feedback.
- Collaboration and Communication: Work closely with UX designers, product managers, and developers to ensure designs are aligned with user needs, business goals, and technical feasibility. Strong communication skills are essential for presenting and explaining design concepts.
- Proficiency with Design Tools: Master industry-standard design and prototyping tools such as Figma, Sketch, Adobe XD, and InVision.
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.
- 9d ago First seen · 79 lines · 53 tokens per session scan A 530b7ad3da36
ui-designer is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 21d ago), licensed MIT. It adds 53 tokens to every session and 1,415 once invoked, about $0.0003 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 cursor rules, from other repositories
external-scale
Source: docs/agents/external-scale.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
mobile-first-ui
Mobile-first UI for settings, dialogs, and lists — smaller type, stacked layouts, nested add dialogs.
frontend-design-direction
Derive a brief-specific visual direction, token sketch, hierarchy, and signature element.