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/agentsorg/design-engineering/review-uigit clone --depth 1 https://github.com/AgentsORG/design-engineeringWhat 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.00029 | $0.00167 |
| Opus 5 | $0.00015 | $0.00084 |
| Sonnet 5 | $0.00006 | $0.00033 |
| Haiku 4.5 | $0.00003 | $0.00017 |
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 2d 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.
What it actually says
Review UI
Spawn or emulate the ui-reviewer subagent (agents/ui-reviewer.md).
- Load
skills/design-engineering/references/meta/review-format.md,review-checklist.md,gotchas.md, andpov.md. - Read the UI code the user pointed at (selection, file, or diff).
- Return only the Before | After | Why table (three to five rows max). Every Why ends with a
[[wikilink]]. - If nothing fails the checklist, say so in one sentence.
Do not add prose around the table unless the user asked for narrative.
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.
- 2d ago First seen · 16 lines · 29 tokens per session scan A ac04e25b3c4d
review-ui is a command published in the GitHub repository AgentsORG/design-engineering (21 stars, last pushed 10d ago), licensed MIT. It adds 29 tokens to every session and 167 once invoked, about $0.0001 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 commands, from other repositories
accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.
design
Focused design session for improving video scene visuals using the frontend-design skill.
handoff
Run the full handoff workflow — specs, measurements, assets, states, and a QA checklist — and output a developer-ready package.
discover
Run a full user research cycle — persona creation, empathy mapping, and journey mapping for a product or feature.
gen-video
Generate video output in one of three modes: Remotion (programmatic React-based video), Gen-AI (shot prompt pack for Runway/Kling/Sora/Pika/Luma), or Remotion+Gen-AI (programmatic scaffold with AI footage embedded).
motion-design
Design micro-interactions, transitions, and animation systems for UI components or full pages.