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 instructions/aztecprotocol/aztec-starter/agents-mdgit 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.00528 | $0.00528 |
| Opus 5 | $0.00264 | $0.00264 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade C, and why
aztec-starter AGENTS.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 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.
- After restarting the local network, always run `rm -rf ./store` to clear stale PXE data. How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidelines for Codex agents
This repository contains TypeScript scripts and Noir contracts for the Aztec network. Follow these guidelines when contributing:
Setup
- Use Node.js v22 with Yarn.
- Install dependencies with
yarn install. - The Aztec CLI (
aztec) must be installed at the version matchingNargo.tomlandpackage.json. - Start the Aztec local network with
aztec start --local-networkbefore running E2E tests or scripts. This is not needed for compilation or Noir unit tests. - After restarting the local network, always run
rm -rf ./storeto clear stale PXE data.
Development
- This is an ESM project (
"type": "module"inpackage.json). - Compile contracts with
yarn compileand generate TypeScript artifacts withyarn codegen. - Use four spaces for indentation in TypeScript and scripts.
- Do not commit generated artifacts (
src/artifacts,target, orstorefolders). - Never edit
src/artifacts/PodRacing.tsdirectly; it is generated byyarn codegen. - To target devnet instead of local network, set
AZTEC_ENV=devnet(e.g.AZTEC_ENV=devnet yarn deploy).
Testing
There are two independent test systems:
- Noir TXE tests (
yarn test:nr): Run in the TXE simulator, no network required. - TypeScript E2E tests (
yarn test:js): Require a running local network. yarn testruns both. Ensure tests pass before committing.
Simulate Before Send
Always call .simulate() before .send() for every state-changing transaction. Simulation runs the transaction locally and surfaces revert reasons immediately instead of waiting for the send timeout with an opaque error.
// Simulate first
await contract.methods.create_game(gameId).simulate({ from: address });
// Then send
await contract.methods.create_game(gameId).send({
from: address,
fee: { paymentMethod },
wait: { timeout }
});
For deployments, store the deploy request to reuse it:
const deployRequest = MyContract.deploy(wallet, ...args);
await deployRequest.simulate({ from: address });
const contract = await deployRequest.send({ ... });
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 · 53 lines · 528 tokens per session scan C 9b4f3fbb6eec
aztec-starter AGENTS.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 528 tokens to every session, about $0.0026 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.