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.
git clone --depth 1 https://github.com/assistant-ui/tool-uiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/assistant-ui/tool-ui/plugin)<a href="https://agentmods.dev/plugins/assistant-ui/tool-ui/plugin"><img src="https://agentmods.dev/badge/plugins/assistant-ui/tool-ui/plugin/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/assistant-ui/tool-ui/plugin"><img src="https://agentmods.dev/badge/plugins/assistant-ui/tool-ui/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 1mo 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
{
"name": "tool-ui",
"description": "Develop assistant-ui tool UIs using Tool UI components",
"version": "0.1.1",
"author": {
"name": "tool-ui"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 89 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 9 lines scan A 2ee5d08b2b41
tool-ui is a plugin published in the GitHub repository assistant-ui/tool-ui (778 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
shadcn
UI component and design system framework. Search registries, install components as source code, and audit your project.
ranui
Reference skill for the ranui web-component library: import map, element inventory, builder/reactivity, accessibility, and pointers to the API docs shipped in the npm package.
decocms-ui
Build UI with the decocms product design system (@decocms/ui).
nightmarquee
Cinematic website prompts plus demo footage, tuned for Lovable, Bolt, Cursor, Claude and Codex. Free prompts need no account.
swiftui-native-component-design
A design process and ready-to-adapt Swift templates for building custom SwiftUI components that feel native — initializer shape, data flow, and ButtonStyle-like customization APIs.
architect-toolkit
Essential architect tools: katas, interview prep, review facilitation, mentoring, anti-patterns, audits, and pattern catalogs.