Borrowing it
Nothing to install: this file belongs to aaddrick/claude-pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aaddrick/claude-pipeline/main/.claude/skills/review-ui/SKILL.mdgit clone --depth 1 https://github.com/aaddrick/claude-pipelineWrote 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/aaddrick/claude-pipeline/review-ui)<a href="https://agentmods.dev/skills/aaddrick/claude-pipeline/review-ui"><img src="https://agentmods.dev/badge/skills/aaddrick/claude-pipeline/review-ui/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/skills/aaddrick/claude-pipeline/review-ui"><img src="https://agentmods.dev/badge/skills/aaddrick/claude-pipeline/review-ui.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.00038 | $0.02370 |
| Opus 5 | $0.00019 | $0.01185 |
| Sonnet 5 | $0.00008 | $0.00474 |
| Haiku 4.5 | $0.00004 | $0.00237 |
Grade A, and why
review-ui 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 13d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Review Skill
Overview
Reviews frontend code against the complete UI design fundamentals specification using parallel bulletproof-frontend-developer agents. Each agent focuses on one design domain, producing a comprehensive, multi-perspective review.
Usage
/review-ui <scope>
Scope can be:
- File path:
/review-ui resources/css/components/buttons.css - Component:
/review-ui resources/views/components/landing/ - Glob pattern:
/review-ui resources/css/**/*.css - Description:
/review-ui "the pricing section on the welcome page"
How It Works
- Scope Identification: Determines what files/components to review
- Parallel Dispatch: Launches independent agent tasks, each focused on one UI fundamentals section
- Compilation: Aggregates findings into a prioritized action list
- Summary: Produces executive summary with critical issues highlighted
Review Domains
Each parallel agent reviews against one of these UI design fundamentals sections:
| Domain | Reference File | Focus Areas |
|---|---|---|
| Grid & Spacing | grid-and-spacing.md |
8pt grid compliance, margins, gutters, white space, alignment |
| Typography | typography.md |
Type scale, font weights, line heights, hierarchy, readability |
| Colors | colors.md |
WCAG contrast (4.5:1+), color roles, 60-30-10 balance, dark mode |
| Buttons | buttons.md |
Anatomy, states, hierarchy, tap targets (44px+), CTAs |
| Forms | forms.md |
Labels, validation, input states, accessibility, sizing |
| Cards | cards.md |
Anatomy, spacing consistency, content truncation, hover states |
| Navigation | navigation.md |
Active states, sticky behavior, mobile patterns, hover |
| Hero Sections | hero-sections.md |
Above the fold, headline hierarchy, CTA placement, social proof |
| Modals & Dropdowns | modals-and-dropdowns.md |
Close methods, focus trap, keyboard nav, overlay |
| Search | search.md |
Placement, autocomplete, no-results handling |
| Shadows & Depth | shadows-and-depth.md |
Elevation levels, shadow direction, dark mode shadows |
| Pricing | pricing.md |
Plan highlighting, feature lists, risk reducers |
| Style Consistency | style-guides.md |
Token usage, naming conventions, component patterns |
What ships with it
2 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.
- 13d ago First seen · 306 lines · 38 tokens per session scan A 5ec1a75ca450
review-ui is a skill published in the GitHub repository aaddrick/claude-pipeline (128 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 2,370 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-30.
Other skills, from other repositories
design-is
Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design…
critique-theater
Five-dimension design quality review — score the artifact against craft, brand, accessibility, and copy, then fix what falls short before handing it over.
ss-lint
Quick automated lint — detects common design system violations in seconds.
nw-fp-usable-design
Naming conventions, API ergonomics, and usability patterns for functional code.
ss-review
Review UI code for design system compliance, accessibility, and best practices.
code-quality-principles
Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.