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/continue)<a href="https://agentmods.dev/commands/benmarte/autoimprove/continue"><img src="https://agentmods.dev/badge/commands/benmarte/autoimprove/continue/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/continue"><img src="https://agentmods.dev/badge/commands/benmarte/autoimprove/continue.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.00921 |
| Opus 5.5 | $0.00005 | $0.00368 |
| Sonnet 5.5 | $0.00002 | $0.00184 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade A, and why
continue 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume an interrupted autoimprove session by reading the log.
Parse $ARGUMENTS:
- If a number is present, use it as the iteration count override. Otherwise use the remaining count from the log.
- If a quoted string is present, use it as the FOCUS override. Otherwise inherit the focus from the interrupted session.
Step 1: Read the log
Read .claude/autoimprove/log.md from the project root.
If the file doesn't exist, stop: "No previous session found. Use /autoimprove:improve to start one."
Step 2: Find the last session
Find the last ## Session — header in the log. If none found (legacy log format), stop: "No resumable session found. The log uses an older format without session headers. Use /autoimprove:improve to start a new session with the updated format."
Step 3: Check session status
Parse the **Status:** line from the last session header.
- If
COMPLETED→ stop: "Last session completed successfully. Use/autoimprove:improveto start a new one." - If
IN_PROGRESSor any other non-COMPLETED value → this session was interrupted. Proceed.
Step 4: Parse session metadata
Extract from the session header:
Planned: total planned iterations (number after "Planned:")Focus: the focus string (text between quotes after "Focus:", or "all improvement areas")Base commit: the commit SHA (text after "Base commit:")Baseline: the baseline score (number before "/100" after "Baseline:")
Step 5: Count completed iterations
Count the number of ## Iteration or ### Iteration headers that appear AFTER the last ## Session — header. This is the completed count.
Step 6: Calculate remaining iterations
remaining = Planned - completed- If the user provided N as an argument, use N instead of
remaining new_total = completed + remaining(orcompleted + Nif overridden)start_at = completed + 1
If remaining ≤ 0 and no N override: stop: "All planned iterations appear to have completed. Use /autoimprove:improve to start a new session."
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 · 98 lines · 12 tokens per session scan A f59a5ab4d4e3
continue is a command published in the GitHub repository benmarte/autoimprove (5 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 921 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
i-have-adhd
Shape output for a reader with ADHD for the rest of this session.
lessons-compact
Compact MEMORY/LESSON.md by deduplicating near-identical lessons, merging same-root-cause lessons, and pruning stale ones — without losing any unique signal. Delegates the analysis to the lessons-compactor agent.
prompt-history
Manage history of created and optimized prompts.
lessons
View project lessons in MEMORY/LESSON.md (project root) and append a compact "never reproduce" lesson.
download
Download Modellix task results to a local directory before the resource URLs expire.
tasks
Inspect Modellix task status and recover tasks after a timeout or unknown submission.