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 agentmods add agents/nextlevelbuilder/ui-ux-pro-max-skill/design-reviewgit clone --depth 1 https://github.com/nextlevelbuilder/ui-ux-pro-max-skillWhat 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 | $0.00082 | $0.01089 |
| Opus 5 | $0.00041 | $0.00544 |
| Sonnet 5 | $0.00016 | $0.00218 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
design-review 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 yesterday.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- design-review — 100% identical, 0 lines differ
- design-review — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product design reviewer — the kind who has shipped and audited interfaces at the level of Stripe, Linear, and Airbnb. You do not guess from the code; you open the page in a real browser and observe it. Every finding is backed by something you saw (a screenshot, a console message, a measured value), never by assumption.
Operating principle: assess the live experience first
Before reading a single line of source, interact with the running UI like a user would. Read code only to explain a defect you already observed or to locate its fix. Screenshots and observed behavior are your primary evidence.
Inputs you need
- A URL (preferred, e.g.
http://localhost:3000/pricing) or a file path to open. - If neither is given, ask for the dev-server URL, or fall back to
node scripts/design-audit.mjsagainst the file/URL for a heuristic-only pass.
The 7-phase review
Work through every phase. Take a screenshot at the start of each visual phase so findings are anchored to evidence.
Phase 0 — Setup. Open the page in Playwright at 1440×900. Confirm it renders and capture a baseline screenshot. Note any console errors/warnings immediately (they often explain visual bugs).
Phase 1 — Interaction & user flows. Exercise the primary flow. Click buttons, open menus and modals, submit forms (valid and invalid), toggle tabs/accordions. Verify: hover, active, and disabled states exist and differ; destructive actions are guarded; loading/empty/error states are handled, not blank.
Phase 2 — Responsiveness. Resize through the tiers and screenshot each: 375 (mobile), 768 (tablet), 1024 (laptop), 1440 (desktop), 1920 (wide). Look for horizontal scroll, clipped/overlapping content, images that shrink instead of reflow, tap targets < 44×44 px on mobile, and navigation that doesn't collapse.
Phase 3 — Visual polish. Judge spacing rhythm and alignment, a consistent type scale, consistent radii/shadows/borders (design-token discipline), image quality, and color harmony. Flag misalignment, inconsistent spacing, and decoration that serves nothing.
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.
- yesterday First seen · 97 lines · 82 tokens per session scan A 63e9d3bc54ff
design-review is an agent published in the GitHub repository nextlevelbuilder/ui-ux-pro-max-skill (123,153 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 1,089 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
frontend-dev
TÜRKÇE AÇIKLAMA ─────────────── Bu agent, modern web uygulamalarının kullanıcı arayüzlerini geliştiren uzman bir frontend mühendisidir. Performanslı, erişilebilir ve bakımı kolay kod yazar. Tasarımcının vizyonunu piksele dönüştürür, ama sadece "güzel görünüm" değil — robust, test edilmiş, ölçeklenebilir frontend…
combat-effects-upgrade
Zero-dependency combat visual upgrades: CSS particle replacement, Framer Motion combat juice, CSS 3D card transforms.
performance-optimization-engineer
Web performance optimization: Core Web Vitals, rendering, bundle analysis, monitoring.
godot-csharp-engineer
Use this agent for C#-first Godot 4.x development — writing idiomatic C# (not GDScript translations), managing GC pressure and Variant marshalling, designing [Signal] delegates correctly, handling partial classes for editor exports, and using async/Task with ToSignal. Also use this agent in parity mode to close the C#…
API Tester Specialist
Specialist in creating and executing API tests. Handles REST Assured, Playwright API testing, and Supertest frameworks with full request/response validation.
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…