Borrowing it
Nothing to install: this file belongs to assistant-ui/tool-ui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/assistant-ui/tool-ui/main/.claude/commands/component.mdgit 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/commands/assistant-ui/tool-ui/component)<a href="https://agentmods.dev/commands/assistant-ui/tool-ui/component"><img src="https://agentmods.dev/badge/commands/assistant-ui/tool-ui/component/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/commands/assistant-ui/tool-ui/component"><img src="https://agentmods.dev/badge/commands/assistant-ui/tool-ui/component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00004 | $0.00164 |
| Opus 5.5 | $0.00002 | $0.00066 |
| Sonnet 5.5 | $0.00001 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
component 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 2mo 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
Create a new component: $ARGUMENTS
Follow project patterns:
- Location:
apps/www/app/components/(or specify subdirectory) - Style: Functional component with TypeScript
- Props: Properly typed interface
- Styling: Tailwind CSS classes
- Exports: Named export (not default)
- Accessibility: ARIA labels, keyboard navigation
- Theme: Support light/dark mode via next-themes
Include:
- TypeScript interface for props
- JSDoc comments for complex logic
- Proper prop validation
- Responsive design considerations
- Error boundaries if needed
Check apps/www/app/components/ for similar patterns to follow.
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.
- 2mo ago First seen · 24 lines · 4 tokens per session scan A 6259cefe9838
component is a command published in the GitHub repository assistant-ui/tool-ui (779 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 164 once invoked, about $0.0000 per session on Opus 5.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
implement-from-plan
You are in implementation-only mode.
plan-component
Before writing code, produce a short plan for the requested UI kit component.
story-and-test
For the component(s) in scope.
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
code-review
Run the code-reviewer subagent on the current diff against origin/development (review-only, no edits).
feature-pipeline
Run this workflow in order in one conversation, unless the user stops between steps.