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/generate-tool-uigit 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.00014 | $0.00548 |
| Opus 5 | $0.00007 | $0.00274 |
| Sonnet 5 | $0.00003 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
generate-tool-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 3d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Tool UI
Create a new Tool UI component through a maintainer-first workflow.
Arguments
$ARGUMENTS
If no arguments are provided, start with the designer interview. If a component slug is provided, use it as the starting point.
Workflow
This command orchestrates 5 specialized agents in sequence:
designer → implementer → (examples ∥ documenter) → reviewer
Execution Steps
1. Design
Launch tool-ui-designer to interview and produce a concrete design spec:
- component slug + label
- serializable schema shape
- action semantics
- receipt semantics (
choice) - accessibility + state behavior
2. Implement
Launch tool-ui-implementer with the design spec.
Implementation must follow current repo contracts:
- scaffold-first:
pnpm component:new <slug>when creating from scratch - schema contract via
defineToolUiContract+parseSerializableX+safeParseSerializableX - receipt prop is
choice(neverconfirmed/decision) - maintain component directory file contract (including
README.md) - update aggregate exports in
apps/www/components/tool-ui/index.ts
3. Examples + Docs (Parallel)
Launch both in parallel:
tool-ui-examples: presets + gallery/showcase decisionstool-ui-documenter: docs page + registry wiring
4. Review
Launch tool-ui-reviewer as the quality gate.
Hard gates:
pnpm lint:cipnpm typecheckpnpm testpnpm registry:check
5. Report
Return a concise summary:
- files created/updated
- any warnings
- final gate status
Critical Registration Points
The documenter/reviewer must ensure all of these are wired:
| File | Purpose |
|---|---|
apps/www/lib/docs/component-registry.ts |
Component metadata + docs nav categorization |
apps/www/lib/docs/preview-config.tsx |
Interactive preview config + ComponentId coverage |
apps/www/app/docs/_components/preset-selector.tsx |
Examples tab preset mapping |
apps/www/app/docs/{name}/page.tsx |
ComponentDocsTabs docs/examples surface |
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.
- 3d ago First seen · 83 lines · 14 tokens per session scan A a3cfd901f625
generate-tool-ui is a command published in the GitHub repository assistant-ui/tool-ui (773 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 548 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
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.