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 commands/phuonghx/aim-cli/optimizegit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/optimize)<a href="https://agentmods.dev/commands/phuonghx/aim-cli/optimize"><img src="https://agentmods.dev/badge/commands/phuonghx/aim-cli/optimize.svg" alt="Measured on agentmods" 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.00009 | $0.00197 |
| Opus 5 | $0.00005 | $0.00098 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
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 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
Code Optimization
Review the provided code or workspace changes for the following issues in order of priority:
- Performance Bottlenecks - Identify O(n²) or inefficient loops, redundant operations, and heavy computations.
- Memory & Resource Efficiency - Find potential leaks, unreleased resources, circular references, or heavy memory consumption.
- Data Structure & Algorithms - Suggest more optimal structures or algorithms.
- Caching & Memoization - Highlight repeated computations that could benefit from caching.
- Concurrency & Async - Point out race conditions, blocking calls, or unoptimized asynchronous operations.
Format your response with:
- Issue Severity (Critical / High / Medium / Low)
- Location in Code (File and line range)
- Problem Statement: Brief explanation of the bottleneck.
- Recommended Solution: Recommended code refactoring with explanation.
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 · 20 lines · 9 tokens per session scan A 0818e615f5f2
optimize is a command published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 197 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
critique-ux
Run a focused UX critique on a screen — affordances, information density, and hierarchy — and output a prioritised fix list.
design-onboarding
Design a first-run experience end to end — activation path, progressive disclosure, and time to first value.
frame-problem
Structure an ambiguous design challenge into a clear problem definition with constraints and criteria.
strategize
Develop a complete UX strategy for a product or feature area.
release
Prepare a release by updating docs and bumping the version.
eg-fix-bug
Fix a bug using the elephant/goldfish workflow — problem doc, goldfish diagnosis check, failing test, fix, review, validate.