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/benmarte/autoimprove/statusgit clone --depth 1 https://github.com/benmarte/autoimproveWhat 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.00011 | $0.00253 |
| Opus 5 | $0.00005 | $0.00127 |
| Sonnet 5 | $0.00002 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
status 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
Read .claude/autoimprove/log.md from the project root.
If the file doesn't exist, say: "No autoimprove runs yet. Use /autoimprove:improve to start."
Otherwise:
Check for interrupted session
Find the last ## Session — header. If found, check its **Status:** line:
-
If
IN_PROGRESS(interrupted session), show:━━━ Last Session: INTERRUPTED ━━━━━━━━━━━━ 📊 Score: [baseline] → [last score] (+delta) 🔁 Completed: N/M iterations (remaining left) 🎯 Focus: "focus string" 💡 Use /autoimprove:continue to resume ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ -
If
COMPLETEDor no session header (legacy format), show the standard summary.
Standard summary
Summarise:
- Total iterations run
- Wins (kept) vs discards
- Score at start vs current
- Top 3 most impactful changes kept
- Last 3 discarded hypotheses (so we don't repeat them)
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 · 35 lines · 11 tokens per session scan A 12dc2504227c
status is a command published in the GitHub repository benmarte/autoimprove (5 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 253 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.
Other commands, from other repositories
crossframe-essay
使用 CrossFrame Essay 把用户给出的主题、素材或问题写成中文批判性洞察文章。.
crossframe-max
Use CrossFrame Max only when the user explicitly asks for maximum CrossFrame mode, exhaustive structural projection, full-scale world-model interpretation, or no word-limit complete explanation.
crossframe-suite
Use this command when a CrossFrame task needs multiple sibling skills in sequence.
crossframe-promax
PROMAX-NAMED-ONLY：只有 crossframe-promax、CrossFrame ProMax、$crossframe-promax、/crossframe-promax 四种明确名称具有触发权。.
crossframe-history
Use CrossFrame History for historical materials, civilization continuity, source-ledger boundaries, dynasty or institutional history, archive-access backlog, FOIA closeout, or local C5 boundary summaries.
crossframe-inquiry
Use CrossFrame Inquiry after a completed CrossFrame diagnosis, article, review, or suite workflow when the user wants follow-up questions, counterexamples, missing evidence, transfer conditions, or action boundaries.