What is update-version?

A repository-wide version-update command for an Aztec project, including its smart-contract and TypeScript code.

Use it to choose an Aztec version, update package and contract references, synchronise the related server, and run tests.

It reduces the chance of missing a version reference or leaving code out of sync after an Aztec release changes its APIs.

How AztecProtocol/aztec-starter configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AztecProtocol/aztec-starter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/AztecProtocol/aztec-starter/next/.claude/commands/update-version.md

Clone the repo

git clone --depth 1 https://github.com/AztecProtocol/aztec-starter

Made for: Claude Code.

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

README.md

[![agentmods](https://agentmods.dev/badge/commands/aztecprotocol/aztec-starter/update-version/github.svg)](https://agentmods.dev/commands/aztecprotocol/aztec-starter/update-version)

Your own site

<a href="https://agentmods.dev/commands/aztecprotocol/aztec-starter/update-version"><img src="https://agentmods.dev/badge/commands/aztecprotocol/aztec-starter/update-version/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/aztecprotocol/aztec-starter/update-version"><img src="https://agentmods.dev/badge/commands/aztecprotocol/aztec-starter/update-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,197 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00030	$0.02197
Opus 5.5	$0.00012	$0.00879
Sonnet 5.5	$0.00006	$0.00439
Haiku 4.5	$0.00003	$0.00220

Measured 2mo ago against content hash 07f87f79d0b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

update-version scanned grade C with 2 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 2mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

1. Clear stale PXE state: `rm -rf ./store`

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsSL "https://install.aztec.network/${VERSION}" | VERSION="${VERSION}" bash -s

.claude/commands/update-version.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update Aztec Version

Update all Aztec version references, sync the MCP server, update contract and TypeScript code for API changes, and run tests.

Version argument: $ARGUMENTS

Workflow

Step 1: Determine the new version

If a version argument is provided, use it directly (strip leading v if present for npm versions, keep v prefix for git tags)
If no version argument, ask the user to provide one

The version has two forms:

npm version (no v prefix): e.g. 4.1.0-devnet.1 — used in package.json, config JSONs, README install command, and CLAUDE.md
git tag (with v prefix): e.g. v4.1.0-devnet.1 — used in Nargo.toml aztec dependency tag and for MCP sync

Step 2: Sync MCP server to new version

Call aztec_sync_repos with the new version tag (with v prefix) and force: true:

aztec_sync_repos({ version: "v<version>", force: true })

Then call aztec_status() to verify the sync succeeded. This gives the MCP server access to the new version's source code and docs — essential for the later steps.

Step 3: Read current files

Read these files to understand current state:

Nargo.toml
package.json
config/local-network.json
config/devnet.json
README.md
CLAUDE.md

Step 4: Update all version references

Use the Edit tool to update each file. Be precise — only change version strings, nothing else.

1. Nargo.toml — Update the aztec dependency tag:

aztec = { git = "https://github.com/AztecProtocol/aztec-nr/", tag = "v<VERSION>", directory = "aztec" }

2. package.json — Update ALL @aztec/* dependency versions to the new npm version (no v prefix). Do NOT change non-aztec dependencies.

3. config/local-network.json — Update settings.version to the new npm version.

4. config/devnet.json — Update settings.version to the new npm version.

5. README.md — Update the install command version in the Getting Started section:

export VERSION=<NEW_VERSION>
curl -fsSL "https://install.aztec.network/${VERSION}" | VERSION="${VERSION}" bash -s

Read the full file on GitHub · 211 lines

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.

2mo ago First seen · 211 lines · 0 tokens per session scan C 07f87f79d0b8

Subscribe to this mod's changes

update-version is a command published in the GitHub repository AztecProtocol/aztec-starter (123 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 2,197 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow

update-version next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
update-versionAztecProtocol/aztec-starter	Command	123	3mo ago	Apache-2.0	C	30	Claude Code
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code
commitechoVic/blade-code	Command	181	24d ago	MIT	A	8	Claude Code
repo-audittractorjuice/arc-kit	Command	2.3k	2d ago	none	A	29	Claude Code
propsmill/infrahub-mcp	Command	10	yesterday	Apache-2.0	A	18	Claude Code
codex-reviewoalders/kitchen-sink	Command	5	3d ago	MIT	A	41	Claude Code

aztec-starter: Command for Claude Code