aztec-starter CLAUDE.md

A project guide for an Aztec starter game, where two players compete through a private smart contract on the Aztec network. Noir is the programming language used for the contract.

In plain words
What is it for?
It helps with building, testing, cleaning, and deploying the Pod Racing contract and its TypeScript artifacts.
Why use it?
It prevents mismatched Aztec versions and directs developers to the correct commands for compiling and generating code.

Instructions file

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 instructions/aztecprotocol/aztec-starter/claude-md
Clone the repo
git clone --depth 1 https://github.com/AztecProtocol/aztec-starter
Per session 2,070 This file is loaded in full into every session.
When invoked 2,070 The same file — it is already loaded in full.
Security scan C 1 finding. 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.02070 $0.02070
Opus 5 $0.01035 $0.01035
Sonnet 5 $0.00414 $0.00414
Haiku 4.5 $0.00207 $0.00207

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

Security

Grade C, and why

aztec-starter CLAUDE.md scanned grade C with 1 finding 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 3d 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.

yarn clear-store # Remove PXE data store (rm -rf ./store)
CLAUDE.md · 186 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

When answering questions about the Aztec network, protocol, SDK, or tooling, fetch https://docs.aztec.network/llms.txt for the current official docs index. Prefer it over training-data knowledge, which may be stale.

Project Overview

Aztec Starter — a Pod Racing game contract built with Noir on the Aztec network. Two players allocate points across 5 tracks over 3 rounds with private state; scores are revealed at the end (commit-reveal pattern). The player who wins more tracks (best of 5) wins.

Aztec version: 5.0.0-rc.2 — pinned across Nargo.toml, package.json, config/*.json, and README. All must stay in sync when updating.

Build & Development Commands

Always use yarn compile or aztec compile to compile contracts, never nargo compile.

yarn compile              # Compile Noir contract (aztec compile)
yarn codegen              # Generate TS artifacts from compiled contract
yarn compile && yarn codegen  # Full rebuild (always run both together)
yarn clean                # Remove compiled artifacts (src/artifacts, target)
yarn clear-store          # Remove PXE data store (rm -rf ./store)

Testing

Two independent test systems:

yarn test:nr              # Noir TXE tests — no network needed, runs in simulator
yarn test:js              # TypeScript E2E tests — requires running local network
yarn test                 # Runs both (test:js then test:nr)

E2E tests require a running local network:

aztec start --local-network   # Start local network first
rm -rf ./store                # Always clear store after network restart

Jest config: jest.integration.config.json — 600s test timeout, ESM mode via ts-jest, matches ./src/**/*.test.ts.

Run a single E2E test:

NODE_NO_WARNINGS=1 node --experimental-vm-modules $(yarn bin jest) --no-cache --runInBand --config jest.integration.config.json -t "test name pattern"

Read the full file on GitHub · 186 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.

  1. 3d ago First seen · 186 lines · 2,070 tokens per session scan C 252020940d4d

Subscribe to this mod's changes

aztec-starter CLAUDE.md is an instructions file published in the GitHub repository AztecProtocol/aztec-starter (122 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,070 tokens to every session, about $0.0103 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.