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/optimize.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/optimize)<a href="https://agentmods.dev/commands/assistant-ui/tool-ui/optimize"><img src="https://agentmods.dev/badge/commands/assistant-ui/tool-ui/optimize/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/optimize"><img src="https://agentmods.dev/badge/commands/assistant-ui/tool-ui/optimize.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.00002 | $0.00158 |
| Opus 5.5 | $0.00001 | $0.00063 |
| Sonnet 5.5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
optimize 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
Analyze and optimize $ARGUMENTS for performance:
-
React Performance
- Unnecessary re-renders
- Missing React.memo/useMemo/useCallback
- Large component trees
- Expensive computations in render
-
Bundle Size
- Heavy dependencies
- Code splitting opportunities
- Dynamic imports for heavy components
- Tree-shaking issues
-
Network
- API call efficiency
- Caching strategies
- Parallel vs sequential requests
- Unnecessary data fetching
-
Runtime
- Algorithm complexity
- Memory leaks
- Event listener cleanup
- Inefficient loops/filters
Provide measurable improvements with before/after comparisons when possible.
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 · 32 lines · 2 tokens per session scan A fe399fc3eaab
optimize is a command published in the GitHub repository assistant-ui/tool-ui (779 stars, last pushed 1mo ago), licensed MIT. It adds 2 tokens to every session and 158 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
fire-resurrect
Autonomous Resurrection Mode — reverse-engineer intent from messy code, then rebuild clean from scratch.
fire-debug
Systematic debugging with persistent state, skills library integration, and WARRIOR validation.
fire-reflect
After any failure (debug resolution, test failure, approach rotation, stalled loop), capture what was tried, why it failed, and what actually worked as a persistent reflection. Future sessions search these before investigating.
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.
feature-pipeline
Run this workflow in order in one conversation, unless the user stops between steps.
refactor
Code-level refactoring analysis and roadmap generation.