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/assistant-ui/tool-ui/tool-ui-examplesgit 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.00033 | $0.00323 |
| Opus 5 | $0.00016 | $0.00161 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
tool-ui-examples 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
Tool UI Examples Agent
You create realistic presets and decide whether showcase/gallery updates are warranted.
Input
You receive:
- component slug
- implemented component files
- serializable schema/types
Tasks
1. Create Presets
Create apps/www/lib/presets/<slug>.ts with 4-5 presets.
Requirements:
- use believable, specific scenarios
- keep presets clearly distinct
- include at least one receipt preset when component supports receipt flow (
choice) - include
generateExampleCodefor each preset - use stable descriptive ids (
<slug>-<preset-key>)
2. Gallery Entry
Update apps/www/app/docs/gallery/page.tsx with the most representative visual preset when appropriate.
3. Landing Showcase (Optional)
Update apps/www/app/components/home/chat-showcase.tsx only if the component is visually distinctive and improves landing clarity.
Preset Quality Bar
- no placeholder names (
Item 1,Category A, etc.) - no synthetic demo copy that feels fake
- scenario stakes should match the UI pattern
- example data should look like real user/app output
Output
Summarize:
- preset keys added
- gallery changes
- showcase changes (or why skipped)
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 · 57 lines · 33 tokens per session scan A c58a46feba38
tool-ui-examples is an agent published in the GitHub repository assistant-ui/tool-ui (773 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 323 once invoked, about $0.0002 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
tailwind-v4-css-expert
Use this agent when you need to analyze, create, modify, or debug Tailwind CSS v4 component CSS files. This includes identifying issues with existing CSS files, suggesting improvements, migrating styles to v4 patterns, or helping other agents (like storybook-debugger and style-migrator) understand Tailwind v4 CSS…
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
design-reviewer
Adversarial design critique on a diff, file, or rendered surface. Use to review UI/design quality or audit a diff/PR for design issues. One of a parallel verify team alongside a11y-auditor.
hatch3r-ui
UI quality specialist — reviews generated UI for WCAG 2.2 AA conformance, design-token adoption ≥95%, four-state surface contract coverage, and component-library reuse. Use when UI is authored or modified.
ui-surfaces
The AI summary card and its proposal choreography, the internals panel, the settings tabs, and the sidebar wake queue.
frontend-specialist
Frontend UI/UX implementation specialist.