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/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/test)<a href="https://agentmods.dev/commands/phuonghx/aim-cli/test"><img src="https://agentmods.dev/badge/commands/phuonghx/aim-cli/test/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/phuonghx/aim-cli/test"><img src="https://agentmods.dev/badge/commands/phuonghx/aim-cli/test.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.00012 | $0.00184 |
| Opus 5.5 | $0.00005 | $0.00074 |
| Sonnet 5.5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
test 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
Expand Unit Tests
Expand the unit test suite for the specified file or module:
- Analyze Coverage: Identify untested branches, functions, and error cases in the target file.
- Determine Testing Framework: Use the project's configured test runner and libraries (e.g. Jest, Vitest, pytest, Go test).
- Write Tests:
- Focus on edge cases (null inputs, empty strings, boundary values, max/min limits).
- Target error handling paths and exceptions.
- Verify asynchronous flows and mock external API dependencies.
- Consistency: Maintain existing test file patterns (e.g.,
*.test.ts,*_test.go,test_*.py) and coding style.
Output the new test code blocks with a brief explanation of what scenarios they cover.
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 · 18 lines · 12 tokens per session scan A 9e402785db08
test is a command published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 184 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-09-03.
Other commands, from other repositories
eg-fix-bug
Fix a bug using the elephant/goldfish workflow — problem doc, goldfish diagnosis check, failing test, fix, review, validate.
test-suite
Run comprehensive test suite with coverage analysis.
generate-widget
Génération Widget Flutter avec Tests.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
create-python-tests
Command "create-python-tests" from codeready-toolchain/tarsy, covering writing tests for python llm service, running tests, from project root, from llm-service/ directory and critical rules.
test-gen
Generate comprehensive tests for a specified file with edge cases and error scenarios.