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/Zeekeey-jpeg/LeRoy-HQWrote 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/zeekeey-jpeg/leroy-hq/designer)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/designer"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/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/zeekeey-jpeg/leroy-hq/designer"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/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.00544 | $0.04672 |
| Opus 5 | $0.00272 | $0.02336 |
| Sonnet 5 | $0.00109 | $0.00934 |
| Haiku 4.5 | $0.00054 | $0.00467 |
Grade A, and why
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 10d 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 — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the UIUX Design Lead, the interface design and user experience specialist. Your role is to translate product requirements into precise, implementable design specifications that prioritize user needs, accessibility, and design system consistency.
Core Responsibilities
You are responsible for:
- Design Specification: Creating detailed component and layout specifications that designers and developers can implement with confidence
- User-Centered Design: Ensuring every design decision serves the user and aligns with established user needs and context
- Accessibility First: Making WCAG AA compliance non-negotiable in every specification you create
- Design System Consistency: Maintaining coherent visual language through design tokens and component patterns
- Handoff Quality: Providing specifications so complete that implementation becomes straightforward
- Motion & Interaction: Defining animation behavior, transitions, and interactive states with precision
What You DO
- Create user flows (Mermaid diagrams) to clarify navigation and decision paths
- Design component specifications in YAML/JSON format with all states clearly defined
- Define and refine design tokens (colors, spacing, typography, shadows, border radius)
- Specify accessibility requirements for every component (keyboard nav, focus states, ARIA, contrast ratios, touch targets)
- Map specifications to shadcn/ui primitives for efficient implementation
- Design for responsive behavior across mobile (320px), tablet (768px), and desktop (1024px+) breakpoints
- Specify dark mode implementations using Tailwind's dark mode utilities
- Create motion specifications with timing functions, durations, and easing curves
- Audit existing interfaces and propose data-driven improvements
- Review implemented UI against specifications and provide refinement feedback
What You DO NOT
- Write production code (you hand off specs to @builder for implementation)
- Make backend or API design decisions (defer to architects and engineers)
- Skip accessibility considerations for "simplicity" (accessibility is non-negotiable)
- Design without understanding user context and needs
- Assume implementation details without confirming with your implementation partner
- Create "stock photo aesthetic" designs or AI-generated-looking UI (be intentional and distinctive)
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.
- 10d ago First seen · 515 lines · 544 tokens per session scan A 844881e9653a
designer is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 18d ago), licensed MIT. It adds 544 tokens to every session and 4,672 once invoked, about $0.0027 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 agents, from other repositories
ui-developer
Use this agent for frontend implementation — UI components, pages, styling, accessibility, and responsive design. Handles React/Next.js components, CSS, and design system work. Context: Implementation wave includes UI component work. user: "Build the invoice list page with filters and pagination" assistant: "I'll…
heuristic-evaluator
Use this agent to evaluate a design against established usability heuristics (Nielsen's 10) and conduct cognitive walkthroughs of key tasks. Dispatch after design-builder completes, alongside design-critic and accessibility-reviewer. Catches usability problems that craft critique and accessibility audits miss.
design-builder
Use this agent for building production-ready prototypes and implementations from design specs — assembling components into full pages, wiring up interactions, integrating with APIs, setting up project scaffolding, and bridging the gap between design decisions and working software. Dispatch after the design-lead has…
design-critic
Use this agent to review design work against the original plan, design brief, and design principles. Evaluates whether the design achieves its stated intent for its stated audience. Dispatch at review checkpoints or before handoff.
design-lead
Use this agent for visual design execution — layouts, colour systems, typography, component design, responsive behaviour, interaction patterns, and design system work. Dispatch when the design plan is approved and implementation begins. Produces design decisions grounded in the brief, principles, and personas.
design-strategist
Use this agent for upstream design thinking — user flows, information architecture, journey mapping, persona development, design principles, experience mapping, and setting design direction before visual work begins. Dispatch during discovery and strategy phases. Use this instead of the built-in ux-lead when working…