upgrade

A command that checks whether the autoimprove add-on has a newer release on GitHub and installs it when available.

In plain words
What is it for?
Keeping autoimprove updated and viewing the changes in its latest release.
Why use it?
It avoids manually checking versions, running the upgrade, and looking up release notes.

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/upgrade
Clone the repo
git clone --depth 1 https://github.com/benmarte/autoimprove
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 258 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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.00011 $0.00258
Opus 5 $0.00005 $0.00129
Sonnet 5 $0.00002 $0.00052
Haiku 4.5 $0.00001 $0.00026

Measured 2d ago against content hash cc4cec6a944d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

upgrade 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 2d 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.

Origin

This is a copy

88% identical to upgrade — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/upgrade.md · 40 lines

What it actually says

Upgrade autoimprove to the latest version. Follow these steps:

Step 1: Check current version

Read the VERSION file in the autoimprove plugin root to get the current version. The plugin root is the directory where this command file lives (go up one level from commands/).

Step 2: Check latest version

Run this command to get the latest release version from GitHub:

gh api repos/benmarte/autoimprove/releases/latest --jq '.tag_name'

Step 3: Compare and upgrade

If the versions match, report: "autoimprove is up to date (v{version})."

If a newer version is available, run the upgrade:

/plugin install autoimprove@autoimprove

Then report:

  • "autoimprove upgraded from v{old} to v{new}."
  • "Restart Claude Code to use the new version."

Step 4: Show changelog

After upgrading, fetch and display the release notes for the new version:

gh api repos/benmarte/autoimprove/releases/latest --jq '.body'
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. 2d ago First seen · 40 lines · 11 tokens per session scan A cc4cec6a944d

Subscribe to this mod's changes

upgrade 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 258 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to upgrade, differing in 16 lines, and is treated as a copy.