improve

A command that runs repeated, automated code-improvement experiments in separate Git worktrees, which are isolated working copies of a repository.

In plain words
What is it for?
Trying a chosen improvement, or scanning for and applying improvements over a set number of iterations.
Why use it?
It lets improvements be tested without changing the main branch, while requiring a configured project and clean working tree first.

Command

Install

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.

agentmods
npx agentmods add commands/benmarte/autoimprove/improve
Clone the repo
git clone --depth 1 https://github.com/benmarte/autoimprove
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 467 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00467
Opus 5 $0.00005 $0.00234
Sonnet 5 $0.00002 $0.00093
Haiku 4.5 $0.00001 $0.00047

Measured yesterday against content hash 4b78bcc32968, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

commands/improve.md · 38 lines

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:

  1. Check .claude/autoimprove/config.md exists. If not, stop: "Run /autoimprove:setup first."
  2. Confirm git working tree is clean. If not, stop: "Please commit or stash changes first."
  3. Run worktree setup (create .claude/autoimprove/worktrees/, update .gitignore).
  4. Run measure skill in the main directory — record as BASELINE.
  5. 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 -N where N = number of wins
  • Remind user: "Review with git log --oneline and git diff HEAD~N before pushing."
Changes

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.

  1. yesterday First seen · 38 lines · 10 tokens per session scan A 4b78bcc32968

Subscribe to this mod's changes

improve is a command published in the GitHub repository benmarte/autoimprove (5 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 467 once invoked, about $0.0001 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-08-31.