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.
npx skills add floomhq/moto --skill ux-auditgit clone --depth 1 https://github.com/floomhq/motoWrote 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/skills/floomhq/moto/ux-audit)<a href="https://agentmods.dev/skills/floomhq/moto/ux-audit"><img src="https://agentmods.dev/badge/skills/floomhq/moto/ux-audit.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.00000 | $0.01793 |
| Opus 5 | $0.00000 | $0.00897 |
| Sonnet 5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00179 |
Grade B, and why
ux-audit scanned grade B with 1 finding 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/ux-audit && mkdir -p /tmp/ux-audit Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Independent UX Audit
Independent UX quality audit using Gemini as the judge. Takes screenshots of live pages at multiple viewports and themes, sends them to Gemini for scoring across 7 UX dimensions. Produces actionable report with per-page breakdown.
Use when user says "ux audit", "audit the ux", "ux score", "design audit", "audit this site", "independent audit", "score the ux", "ux review", or wants an independent design evaluation of a website.
Arguments
/ux-audit <url>-- quick mode: screenshot-based scoring (default)/ux-audit <url1> <url2> ...-- audit specific pages/ux-audit <url> --focus "mobile, typography"-- audit with focus areas/ux-audit deep <url>-- deep mode: Gemini autonomously browses and tests the site/ux-audit deep <url> --auth <login_url> <user> <pass>-- deep mode with auth credentials
Workflow
Step 1: Prepare
rm -rf /tmp/ux-audit && mkdir -p /tmp/ux-audit
Parse the arguments to get the list of URLs to audit. If only a domain is given (e.g., https://example.com), infer the key pages (typically /, /about, /pricing, /waitlist, /docs).
Step 2: Capture Screenshots
Use chrome-devtools MCP tools for screenshot capture. For EACH URL:
2a. Navigate and prepare:
navigate_page(type="url", url="<URL>")
Wait for load, then force any reveal animations:
evaluate_script: () => {
document.querySelectorAll('[data-reveal]').forEach(el => el.setAttribute('data-reveal', 'visible'));
return 'ready';
}
2b. Desktop Light (1280x800):
evaluate_script: () => { document.documentElement.dataset.theme = 'light'; return 'light'; }
Wait 1s, then:
take_screenshot(fullPage=true, filePath="/tmp/ux-audit/{slug}-desktop-light.png")
2c. Desktop Dark:
evaluate_script: () => { document.documentElement.dataset.theme = 'dark'; return 'dark'; }
Wait 1s, then:
take_screenshot(fullPage=true, filePath="/tmp/ux-audit/{slug}-desktop-dark.png")
2d. Resize to mobile:
resize_page(width=390, height=844)
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 · 208 lines · 0 tokens per session scan B 1cd78893cf1d
ux-audit is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,793 tokens. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ui-review
Retroactive visual audit of UI implementation with 1-4 scoring per dimension.
claude-design-patterns
Engineering rules and reusable patterns for building polished web UI, React artifacts, slide decks, animations, and device mockups — distilled from Anthropic's leaked Claude Design agent system prompt. Use ALONGSIDE the frontend-design skill whenever building or iterating on visual web output: single-file React/HTML…
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
self-assessment
Interactive skill assessment with personalized learning path generation.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.