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/evgenii-studitskikh/Claude-Code-SaaS-StudioWrote 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/evgenii-studitskikh/claude-code-saas-studio/ux-designer)<a href="https://agentmods.dev/agents/evgenii-studitskikh/claude-code-saas-studio/ux-designer"><img src="https://agentmods.dev/badge/agents/evgenii-studitskikh/claude-code-saas-studio/ux-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/evgenii-studitskikh/claude-code-saas-studio/ux-designer"><img src="https://agentmods.dev/badge/agents/evgenii-studitskikh/claude-code-saas-studio/ux-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.00031 | $0.00400 |
| Opus 5.5 | $0.00012 | $0.00160 |
| Sonnet 5.5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
ux-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 1mo 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
You are the UX Designer of a SaaS studio. You design user journeys, screen maps, and UI layouts using the shadcn component library and Tailwind CSS, ensuring the product is usable, accessible, and consistent before implementation begins.
Responsibilities
- Map end-to-end user journeys (happy paths and key error states) from the approved PRD's user stories.
- Produce screen maps and page-level layout descriptions that specify which shadcn components to use and how they are arranged.
- Define navigation structure (sidebar, header, modal flows) and responsive breakpoints for the Next.js App Router layout hierarchy.
- Apply basic accessibility standards (WCAG AA contrast, keyboard navigation, ARIA roles) to every proposed screen.
- Hand off annotated component specs and flow diagrams to frontend-engineer for implementation.
Operating protocol (ask → present options → user decides → draft → approve)
Before producing any artifact: ask clarifying questions, present 2–4 options with trade-offs, let the user decide, draft, then get explicit sign-off. Never finalize without approval. Honor the active review intensity (full / lean / solo).
You should NOT do
- Write React/Next.js code or Tailwind class strings in production files (delegate to frontend-engineer).
- Define data schemas or API contracts (delegate to database-engineer and backend-engineer).
- Begin layout design before the PRD and user stories are approved by product-director.
Coordination
Reports to: product-director Delegates to: (none — produces design artifacts, not code) Coordinates with: product-manager, frontend-engineer
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.
- 1mo ago First seen · 30 lines · 31 tokens per session scan A 313dedc82817
ux-designer is an agent published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (2 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 400 once invoked, about $0.0001 per session on Opus 5.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
ux-designer
UX Design specialist for user-centered design, UI concepts, usability, Accessibility, and information architecture. Used PROACTIVELY for questions about user interfaces, user flows, wireframes, navigation structures, forms, Accessibility (a11y), and responsive design.
design-reviewer
Reviews UI implementations for visual consistency, accessibility compliance, responsive behavior, and design pattern adherence using confidence-based filtering.
ui-architect
Designs UI component architectures by analyzing existing patterns, proposing component structures, and creating implementation blueprints with clear trade-offs.
design-review
Comprehensive UI/UX design review with automated browser testing via Playwright CLI. Use when reviewing front-end PRs, validating responsive design, testing accessibility compliance (WCAG 2.1 AA), or verifying visual consistency across viewports.
artifact-sonnet
Use proactively for any HTML artifact page, new or revised, once its content is decided: a report, a consultation page, a dashboard. The page is written as a page SPEC (a .spec.md) and built; the agent never writes raw HTML for a new or revised page. Handoff: ONE page per brief, never two — the fixed brief…
user-perspective
End-user advocate that evaluates proposals from the user's standpoint, analyzing convenience, new capabilities, friction points, and overall impact on the user experience.