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/commitgit 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/commit)<a href="https://agentmods.dev/commands/phuonghx/aim-cli/commit"><img src="https://agentmods.dev/badge/commands/phuonghx/aim-cli/commit.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 | $0.00006 | $0.00207 |
| Opus 5 | $0.00003 | $0.00103 |
| Sonnet 5 | $0.00001 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
commit 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 yesterday.
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
Context
- Current git status: !
git status - Current git diff: !
git diff HEAD - Current branch: !
git branch --show-current - Recent commits: !
git log --oneline -10
Your task
Based on the above changes, create a single git commit.
If a message was provided via arguments, use it: $ARGUMENTS
Otherwise, analyze the changes and create an appropriate commit message following Conventional Commits format:
feat:for new featuresfix:for bug fixesdocs:for documentation changesrefactor:for code refactoringtest:for adding testschore:for maintenance tasks
Provide a concise subject and description if the change is significant.
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.
- yesterday First seen · 29 lines · 6 tokens per session scan A 6049491708d6
commit is a command published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 2mo ago), licensed MIT. It adds 6 tokens to every session and 207 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
git-commit
Create a git commit for the current changes using Conventional Commits-style format.
eg-precommit-review
Run the pre-commit independent-reviewer loop on the current branch's pending changes.
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.
release
Prepare a release by updating docs and bumping the version.