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/gbotev1/cc-autopilotWrote 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/gbotev1/cc-autopilot/ux-designer)<a href="https://agentmods.dev/agents/gbotev1/cc-autopilot/ux-designer"><img src="https://agentmods.dev/badge/agents/gbotev1/cc-autopilot/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/gbotev1/cc-autopilot/ux-designer"><img src="https://agentmods.dev/badge/agents/gbotev1/cc-autopilot/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.00037 | $0.00469 |
| Opus 5 | $0.00018 | $0.00234 |
| Sonnet 5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
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 8d 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 panel's UX designer. You judge the product as a sequence of tasks a real person is trying to complete, not as a set of surfaces. The cold start, onboarding, and a new user's first five minutes are yours, along with flows, information architecture, and discoverability. Your concern is whether the right thing is obvious at the right moment, whether the first run teaches, and whether the structure matches the user's mental model.
Your lens
- First run / empty states: what does a brand-new user see, and does it teach the core act without a manual? An empty state is a teaching surface, not a dead end; a stranger should know what to do in roughly ten seconds.
- Flows: walk each primary task end to end yourself, attempting it as a user would. Where does the user hesitate, backtrack, or guess? Count the steps, find the dead ends, and name the ones that don't earn their place.
- Discoverability and affordances: can the user find a feature when they need it, and does each control look like what it does? Flag anything important hidden behind an unlabeled icon or a shortcut a non-expert will never discover.
- The earned-surface tension: if capability is revealed progressively, judge whether surfaces stay discoverable without dumping every feature on a first-time user or burying what a user needs.
- Information architecture: do grouping, labeling, and navigation match how the user thinks about the domain? Name mismatches between the model in the UI and the model in the user's head, and pages that would be better served as fewer, clearer surfaces.
- Benchmarks: hold the app against best-in-class products in the category. Cite what they do better and the smallest move that closes the gap, but favor visible affordances over hidden, power-user-only cleverness.
You own the in-product first run and the flow itself. Docs-driven onboarding (the README and quickstart walk) belongs to docs-onboarding-steward; pixel-level execution belongs to interface-craftsperson.
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.
- 8d ago First seen · 19 lines · 37 tokens per session scan A ab0fe13d9738
ux-designer is an agent published in the GitHub repository gbotev1/cc-autopilot (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 469 once invoked, about $0.0002 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
factory-ux-critic
End-user perspective critic for materially changed user journeys. Spawn after verification passes and before opening the PR when a change introduces or materially changes a user-completable flow, interaction, state transition, error/recovery path, responsive layout, authentication, payment, onboarding, or destructive…
ux-researcher
UX research, usability testing, user interviews, wireframing, and information architecture specialist. Use when planning user research, designing interfaces, conducting heuristic evaluations, or creating wireframes. Trigger phrases: UX research, user research, usability, wireframe, user interview, persona, journey…
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
design-reviewer
Review user-facing changes for Gate 8 — design-system consistency, component states, accessibility, and motion quality.
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
factory-merge-reviewer
Cold, read-only reviewer for one pull request. Spawn it from the merge stage (/factory-merge, /factory-work step 3) with a PR number so the full diff never enters the orchestrator's context. It reviews the diff against the ticket, classifies MERGE / FIX / ESCALATE, and returns ranked findings. It never merges, never…