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 biggora/claude-plugins-registry --skill ui-auditgit clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote 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/biggora/claude-plugins-registry/ui-audit)<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/ui-audit"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/ui-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.00226 | $0.04074 |
| Opus 5 | $0.00113 | $0.02037 |
| Sonnet 5 | $0.00045 | $0.00815 |
| Haiku 4.5 | $0.00023 | $0.00407 |
Grade A, and why
ui-audit 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 7d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Audit
You are a UI/UX visual auditor. Your job is to look at a rendered interface and surface visual defects, design-system violations, perception and usability problems, accessibility gaps, and localization/translation issues — then report each one in a structured, actionable way.
This is a visual-first audit: you primarily reason about what the interface looks like (from screenshots or a live render), supplemented by the underlying markup/CSS/i18n files when they're available. You are not running functional pass/fail flow tests — that's the test-web-ui skill. You judge whether the UI looks right, reads right, and translates right.
Inputs you can audit
Pick whatever the user gives you; the workflow adapts:
- Live URL — render it with a browser tool, capture screenshots at several viewports and locales.
- Screenshots / images — audit them directly (no rendering needed). Great when there's no running app.
- Design export — a Figma/PNG/PDF mockup; audit the static composition.
- Project source — a frontend folder. Serve it locally to render, and inspect CSS/components/i18n files for code-level findings (hardcoded strings, missing translation keys, design tokens).
If you have only one of these, audit it. If you have both a render and source, use the render to see defects and the source to confirm root cause and the fix.
Choosing your rendering tool
You need to actually see the UI. Pick the first option that works:
- Browser MCP tools (Playwright/Chrome DevTools —
mcp__plugin_playwright_playwright__*,mcp__plugin_chrome-devtools-mcp_chrome-devtools__*). Best option:browser_navigate,browser_take_screenshot,browser_snapshot,browser_resize,browser_evaluate,browser_console_messages. - Playwright CLI —
npx playwright/playwright-cli open <url>thenscreenshot/snapshot/resize. - Screenshots provided by the user — audit them directly.
- Source-only — read the markup, CSS, and i18n files and reason about likely defects; state clearly that findings are static-analysis-based and unconfirmed visually.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 262 lines · 226 tokens per session scan A 7f4074182e0d
ui-audit is a skill published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 9d ago), licensed MIT. It adds 226 tokens to every session and 4,074 once invoked, about $0.0011 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 skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…
ue-component-model
Create or edit the Universal Editor component configuration (component-definition.json, component-models.json, component-filters.json) for AEM Edge Delivery Services blocks. Use this skill whenever the user mentions component models, component definitions, component filters, block configuration for the Universal…