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/aztecprotocol/aztec-starter/update-versiongit clone --depth 1 https://github.com/AztecProtocol/aztec-starterWhat 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.00030 | $0.02197 |
| Opus 5 | $0.00015 | $0.01099 |
| Sonnet 5 | $0.00006 | $0.00439 |
| Haiku 4.5 | $0.00003 | $0.00220 |
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 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.
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 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
vif present for npm versions, keepvprefix for git tags) - If no version argument, ask the user to provide one
The version has two forms:
- npm version (no
vprefix): e.g.4.1.0-devnet.1— used inpackage.json, config JSONs, README install command, andCLAUDE.md - git tag (with
vprefix): e.g.v4.1.0-devnet.1— used inNargo.tomlaztec 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.tomlpackage.jsonconfig/local-network.jsonconfig/devnet.jsonREADME.mdCLAUDE.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
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.
- 2d ago First seen · 211 lines · 0 tokens per session scan C 07f87f79d0b8
update-version is a command published in the GitHub repository AztecProtocol/aztec-starter (122 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 2,197 once invoked, about $0.0002 per session on Opus 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.