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/assistant-ui/tool-ui/reviewgit clone --depth 1 https://github.com/assistant-ui/tool-uiWhat 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.00004 | $0.00177 |
| Opus 5 | $0.00002 | $0.00088 |
| Sonnet 5 | $0.00001 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
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 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 $ARGUMENTS for:
-
Security Issues
- XSS vulnerabilities
- Unsafe user input handling
- API key exposure
- OWASP Top 10 concerns
-
Performance
- Unnecessary re-renders
- Missing memoization
- Large bundle impacts
- Inefficient algorithms
-
Type Safety
- Missing TypeScript types
- Unsafe
anyusage - Type assertions that could fail
-
Best Practices
- React hooks rules
- Component composition
- Error boundaries
- Accessibility (a11y)
-
Code Quality
- Readability
- Maintainability
- DRY principle violations
- Magic numbers/strings
Provide specific line references and actionable fixes.
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 · 36 lines · 4 tokens per session scan A c7a7501d524e
review is a command published in the GitHub repository assistant-ui/tool-ui (773 stars, last pushed 3mo ago), licensed MIT. It adds 4 tokens to every session and 177 once invoked, about $0.0000 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
zag
Implement a Zag.js component in Ark UI.
finalize
Pre-ship gate — runs detector, verifies brief and tokens, applies the 10-pass finish bar, ranks findings by feedback hierarchy. Use when the user wants to ship, merge, or finalize a surface and needs a verdict (READY / NOT READY / BLOCKED) before committing.
sddesign
Full spec-driven pipeline — walks brief → tokens → shape (spec) → craft (build) → converge → ship in one guided run. Writes .ui-craft/spec.md. Run when starting a net-new surface from scratch.
shape
Wireframe-first pass — outputs an ASCII layout + state list + content inventory + question list before any code. Use when starting a new screen from scratch or when the user's brief is still ambiguous.
tokens
Audit or establish the project's 3-layer token spine.
craft
One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface ("build me a dashboard", "I need a landing page") and expects a shippable result, not component-level help.