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.
/plugin marketplace add assistant-ui/tool-uinpx agentmods add plugins/assistant-ui/tool-ui/plugingit clone --depth 1 https://github.com/assistant-ui/tool-uiGrade 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 yesterday.
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 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.
- yesterday First seen · 9 lines scan A 2ee5d08b2b41
tool-ui is a plugin published in the GitHub repository assistant-ui/tool-ui (773 stars, last pushed 3mo 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
ran
Skills for the ran monorepo libraries — ranui (web components) and ranuts (utilities) — so AI can read and use them without spelunking the source. Install whichever you use.
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.
ranuts
Reference skill for the ranuts utility library: 4-entry import map, ranuts/utils inventory, conventions, and pointers to the API docs shipped in the npm package.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
vibing-nvim
Neovim MCP tools, skills, and subagents for vibing.nvim — lets Claude Code read/edit buffers, drive LSP, and manage windows in a running Neovim instance.