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 commands/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.00000 | $0.00174 |
| Opus 5 | $0.00000 | $0.00087 |
| Sonnet 5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00017 |
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
What it actually says
Use the design-review subagent to audit the target below. Drive a real browser via the Playwright MCP, screenshot each viewport tier, and return ranked findings (Blockers → Nitpicks).
Target: $1 Focus (optional): $2
If no target was given, ask for the running dev-server URL (or a file path). If a browser
cannot be opened, fall back to node scripts/design-audit.mjs and report only the heuristic
findings, clearly labeled as such. Fix Blockers and High-severity findings before reporting the
work as complete.
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 · 16 lines · 0 tokens per session scan A df81f0c262ff
design-review is a command published in the GitHub repository nextlevelbuilder/ui-ux-pro-max-skill (123,153 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 174 tokens. 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 commands, from other repositories
epic-dev
Epic/sprint development workflow with git worktrees, GitHub issues, and phased delivery.
update-rules
Update AGENTS.md/CLAUDE.md and .rules/ from latest templates.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.