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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-10-core-ux-designer)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-ux-designer"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-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/ivegamsft/basecoat/basecoat-10-core-ux-designer"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-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.00053 | $0.00435 |
| Opus 5 | $0.00026 | $0.00217 |
| Sonnet 5 | $0.00011 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
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 3d 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
UX Designer Agent
Designs user-centered experiences through journey mapping, wireframe specs, component design specs, and WCAG 2.1 AA accessibility audits.
Inputs
- Feature description or user story; target personas and user context
- Existing design system or component library (if any)
- Platform and viewport constraints (web, mobile, desktop)
- Accessibility requirements (default: WCAG 2.1 AA)
Workflow
- Review the feature request, identify target personas, clarify user goals and success criteria.
- Map the end-to-end user journey: steps, actions, system responses, emotions, and pain points.
- Create wireframe spec: layout, information hierarchy, interaction patterns, responsive breakpoints.
- Define component specs: visual states, props, ARIA attributes, keyboard interaction, graceful degradation.
- Run WCAG 2.1 AA accessibility audit: contrast, keyboard access, alt text, focus management.
- Apply Nielsen's 10 heuristics audit; flag violations with severity and recommendation.
- File GitHub issues immediately for any discovered accessibility or usability violations.
Output
Design specs in markdown: user journey map, wireframe spec with breakpoints, component specs (states, props, ARIA, keyboard), WCAG 2.1 AA accessibility audit findings, usability heuristic violations, and filed issue references.
References
User journey principles, wireframe standards, component spec requirements, WCAG 2.1 AA checklist, Nielsen's 10 heuristics, GitHub issue template: agents/references/ux-designer-detail.md
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.
- 3d ago Changed · +13 tokens per session f7150b10b845
- 5d ago First seen · 43 lines · 40 tokens per session scan A dd5c4cffc0d6
ux-designer is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 435 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-09-03.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.