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/benmarte/autoimproveWrote 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/benmarte/autoimprove/improve)<a href="https://agentmods.dev/commands/benmarte/autoimprove/improve"><img src="https://agentmods.dev/badge/commands/benmarte/autoimprove/improve/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/benmarte/autoimprove/improve"><img src="https://agentmods.dev/badge/commands/benmarte/autoimprove/improve.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.00010 | $0.00467 |
| Opus 5.5 | $0.00004 | $0.00187 |
| Sonnet 5.5 | $0.00002 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
improve 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
Parse $ARGUMENTS:
- If a number is present, use it as the iteration count. Otherwise default to 5.
- If a quoted string is present (e.g.
"Replace fetch() with apiClient"), use it as the FOCUS for this run. - Both can be combined:
/autoimprove:improve 10 "Fix any types in convex/"→ 10 iterations, focused on that task.
Start the autoimprove loop for the parsed iteration count.
Pre-flight:
- Check
.claude/autoimprove/config.mdexists. If not, stop: "Run /autoimprove:setup first." - Confirm git working tree is clean. If not, stop: "Please commit or stash changes first."
- Run worktree setup (create
.claude/autoimprove/worktrees/, update.gitignore). - Run measure skill in the main directory — record as BASELINE.
- Print the pre-flight summary with progress indicators:
━━━ Pre-flight ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✓ Config found ✓ Git working tree clean ✓ Worktree directory ready ✓ Baseline score: XX/100 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Starting N iterations. Focus: [focus or "all improvement areas"] Main branch is safe — experiments run in isolated worktrees.
Run the improve-loop skill for the requested number of iterations, passing the FOCUS string if one was provided. Pass session_mode: new so it creates a fresh session header in the log.
After all iterations — session summary:
- Clean up all remaining worktrees (worktree skill cleanup step)
- Report: total iterations, wins vs discards, baseline → final score
- List all commits added to main (one per winning experiment)
- Show:
git log --oneline -Nwhere N = number of wins - Remind user: "Review with
git log --onelineandgit diff HEAD~Nbefore pushing."
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 · 38 lines · 10 tokens per session scan A 4b78bcc32968
improve is a command published in the GitHub repository benmarte/autoimprove (5 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 467 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-31.
Other commands, from other repositories
fix-pr-comments
Systematically resolve Pull Request review comments using gh CLI to fetch comments and apply requested changes.
odoo-review
Review a GitHub PR against Odoo PSDU conventions — business need, file-by-file, then full-logic; before/after fixes; terminal-only, read-only.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
worktree
Manage git worktrees for isolated feature development.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
genshijin-review
A compact Japanese-language code-review command that reports one finding per line with a severity label and suggested fix.