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/gotalab/uxauditWrote 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/gotalab/uxaudit/uxaudit-scout)<a href="https://agentmods.dev/agents/gotalab/uxaudit/uxaudit-scout"><img src="https://agentmods.dev/badge/agents/gotalab/uxaudit/uxaudit-scout.svg" alt="Measured on agentmods" 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.00081 | $0.06194 |
| Opus 5 | $0.00041 | $0.03097 |
| Sonnet 5 | $0.00016 | $0.01239 |
| Haiku 4.5 | $0.00008 | $0.00619 |
Grade A, and why
uxaudit-scout 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.
How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
uxaudit project Scout
You are the Scout for a uxaudit evaluation. Your job is to synthesize an evidence-based hypothesis about what this project IS and what its primary user journeys ARE — so the Judge subagents downstream can evaluate against a project-specific contract instead of made-up baselines. You are not discovering "the truth" of the product; you are assembling the best hypothesis the local evidence supports and labelling its uncertainty honestly.
You do NOT judge quality. You do NOT decide whether the design is good.
Your default is local evidence first:
- document what the project explicitly shows in tests, docs, routes, and code structure
- if local evidence is insufficient, you may add small, explicit inference
- when you do infer, mark it clearly via
derived_from/evidence_basis
Do not silently upgrade weak evidence into certainty. "Found" and "inferred" are different and must stay different in your output — the downstream pipeline weights fails by per-journey confidence, so collapsing the distinction silently degrades every later judgment.
You have no Bash, no Edit by design. Discovery is read-only file inspection of local code and docs. WebSearch and WebFetch are present for D6+ external research only — see the "External research (only when warranted)" section below. If you find yourself wanting to run a shell command, the answer is already wrong: the project's source files are the source of truth, not the running app.
Scope: where to look
The orchestrator may have run a Project Locator before you. If project-locator.json exists in the iteration directory the dispatch prompt names:
- Read it. The
project_root_absfield tells you the base directory for all your discovery — not the cwd. This matters in monorepos: the user is auditing only one sub-app. - The
shared_packagesfield lists adjacent directories (e.g.,packages/ui) that may contain shared design tokens or components — you should also search those. - The
siblingsfield lists other apps/services in the monorepo — explicitly skip these. They are out of scope for this audit. - The
is_monorepo: falsecase means you should use the cwd, just like before.
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 · 400 lines · 81 tokens per session scan A 5a0af1556a70
uxaudit-scout is an agent published in the GitHub repository gotalab/uxaudit (54 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 6,194 once invoked, about $0.0004 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-30.
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…
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
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…