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/aim-docs)<a href="https://agentmods.dev/commands/phuonghx/aim-cli/aim-docs"><img src="https://agentmods.dev/badge/commands/phuonghx/aim-cli/aim-docs/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/aim-docs"><img src="https://agentmods.dev/badge/commands/phuonghx/aim-cli/aim-docs.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.00013 | $0.00237 |
| Opus 5.5 | $0.00005 | $0.00095 |
| Sonnet 5.5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
aim-docs 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
Documentation Management
Manage documentation files under the .ai-context/docs/ directory to maintain a clear and up-to-date project context.
Instructions:
- If listing docs is requested, run
aim doc listto see all current documentation files. - If viewing a doc is requested, run
aim doc view <path>(e.g.aim doc view architecture/auth) to read it. - If creating or rewriting a doc is requested:
- To create: Run
aim doc create "<title>" -d "<desc>" -f [folder]to initialize the document template. - To rewrite: Use file editing tools to update the markdown file under
.ai-context/docs/(retaining proper metadata at the top). - Ensure the rewrite contains clear structure (single H1, metadata block, overview), practical code examples (no placeholders), and cross-references (
@task-Nor@doc/<path>).
- To create: Run
- Run
aim validateto ensure all links and references in the documentation are healthy and pointing to valid targets.
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 · 17 lines · 13 tokens per session scan A 6f88d3b6094d
aim-docs is a command published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 237 once invoked, about $0.0001 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
dejavu-docs
Search project documentation embeddings via dejavu (docs-only).
output
Generate output artifacts from active wiki content — summaries, reports, study guides, slide outlines, timelines, glossaries, comparisons. Outputs are filed back into the wiki.
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.
spreadsheet-audit
Perform a 6-step audit of an Excel spreadsheet for formula correctness, formatting consistency, data integrity, boss-auditable simplicity, and spec compliance. Uses the excel-screenshot MCP server tools — no Excel installation required.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.