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-documentergit 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.00030 | $0.00404 |
| Opus 5 | $0.00015 | $0.00202 |
| Sonnet 5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
tool-ui-documenter 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 Documenter Agent
You document new components and wire them into docs/examples surfaces.
Input
You receive:
- component slug + label
- implemented component + schema
- presets from
apps/www/lib/presets/<slug>.ts
Required Work
1. Create docs page files
Create/update:
apps/www/app/docs/<slug>/page.tsxapps/www/app/docs/<slug>/content.mdxapps/www/app/docs/<slug>/opengraph-image.tsx
Rules:
page.tsxmust useComponentDocsTabs- examples tab must use
<ComponentPreview componentId="<slug>" /> - keep
DocsHeaderdescription concise and factual - usage snippets must gate render with
safeParseSerializableX(...)and returnnullon parse failure
2. Register docs metadata + previews
Update all of:
apps/www/lib/docs/component-registry.tsapps/www/lib/docs/preview-config.tsxapps/www/app/docs/_components/preset-selector.tsx
3. Keep docs aligned with maintainer contracts
Document:
- source/install paths in
apps/www/components/tool-ui/<slug> - serializable contract + parse helpers
- action + receipt behavior (use
choiceterminology) - accessibility notes for interaction-heavy components
Verification Checklist
- docs page renders with docs/examples tabs
- component appears in docs navigation
- examples tab resolves presets for
<slug> - preview config has matching
ComponentId+ render mapping - content avoids outdated receipt language (
confirmed,decision)
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 · 60 lines · 30 tokens per session scan A 4953000c92eb
tool-ui-documenter is an agent published in the GitHub repository assistant-ui/tool-ui (773 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 404 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
Accessibility Expert
Expert assistant for web accessibility (WCAG 2.1/2.2), inclusive UX, and a11y testing.
react-frontend
Use this agent PROACTIVELY when building React user interfaces, creating components, implementing pages, managing state, styling with Tailwind, handling forms, or optimizing frontend performance. Invoke for any React 19+, Next.js 15+, or TypeScript frontend work including Server Components, Server Actions, and modern…
style-migrator
Use this agent when you need to migrate HeroUI components from TypeScript-based styles (.styles.ts files using tailwind-variants) to CSS-based styles (.css files) following the BEM naming convention. This includes converting tv() configurations to CSS classes, maintaining variant mappings, and ensuring all visual…
storybook-debugger
Use this agent when you need to debug and fix issues in the HeroUI Storybook development environment, particularly CSS transformation errors, Tailwind CSS v4 compatibility issues, or component styling problems. This includes investigating build errors, runtime errors in the browser, and issues with the CSS-to-JS…
component-example-researcher
Use this agent when you need to discover and suggest new examples for Ark UI components. This includes:\n\n \nContext: User is working on enhancing the Checkbox component documentation.\nuser: "I've just finished updating the Checkbox component API. Can you help me find what examples we should add?"\nassistant: "I'll…
Update Copilot CompletionAlgorithm
Synchronize this repository's Copilot completion behavior with a pinned microsoft/vscode commit while preserving reviewed completion effects and provenance.