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/a16z/jolt/claude-mdgit clone --depth 1 https://github.com/a16z/joltWrote 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.
[](https://agentmods.dev/instructions/a16z/jolt/claude-md)<a href="https://agentmods.dev/instructions/a16z/jolt/claude-md"><img src="https://agentmods.dev/badge/instructions/a16z/jolt/claude-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.05276 | $0.05276 |
| Opus 5 | $0.02638 | $0.02638 |
| Sonnet 5 | $0.01055 | $0.01055 |
| Haiku 4.5 | $0.00528 | $0.00528 |
Grade A, and why
jolt CLAUDE.md 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project Overview
Jolt is a zkVM (zero-knowledge virtual machine) for RISC-V (RV64IMAC) that efficiently proves and verifies program execution. It uses sumcheck-based protocols, multilinear polynomial commitments (Dory), and the Twist/Shout lookup argument.
Essential Commands
Linting and Formatting
# Must pass in both standard and ZK modes
cargo clippy --all --features host -q --all-targets -- -D warnings
cargo clippy --all --features host,zk -q --all-targets -- -D warnings
cargo fmt -q
Testing
# Always cargo nextest, never cargo test
cargo nextest run --cargo-quiet
# Run specific test in specific package
cargo nextest run -p [package_name] [test_name] --cargo-quiet
# Primary correctness check — run muldiv e2e test in both modes
cargo nextest run -p jolt-prover-legacy muldiv --cargo-quiet --features host
cargo nextest run -p jolt-prover-legacy muldiv --cargo-quiet --features host,zk
# Modular prover acceptance suites (mirror CI): clear-mode byte-diff ratchets
# vs the legacy prover, and the modular ZK e2e (muldiv accept, tamper reject,
# advice, committed program)
cargo nextest run -p jolt-prover --features prover-fixtures --cargo-quiet
cargo nextest run -p jolt-prover --features prover-fixtures,zk --cargo-quiet
Building
# Prefer clippy over build for validation. Only build when preparing to execute a binary.
cargo build -p jolt-prover-legacy -q
# After pulling changes, reinstall the jolt CLI or guest builds may fail.
cargo install --path . --locked
Profiling
# Modular prover (primary): emits benchmark-runs/{timestamp}_modular_{name}_{scale}/ containing trace.json
# (Perfetto UI / trace_processor SQL), summary.json (machine-queryable), and memory.html,
# with benchmark-runs/latest_modular_{name}_{scale} symlinked to the newest successful run.
cargo run --release -p jolt-prover --features profiling -- profile --name fibonacci --format chrome
# --name options (default scale): fibonacci (16), sha2-chain (22), sha3-chain (22), btreemap (20)
# --scale <log2 trace length> overrides; --format none = no-subscriber Instant baseline
# --backend reference (default, naive test oracle) | optimized (performance tier, legacy-parity);
# optimized artifacts get an _optimized suffix on the run dir and latest_ symlink
# Canonical summary queries (no Perfetto UI needed) — see book/src/usage/profiling/zkvm_profiling.md
jq '.stages | map({label, s: (.wall_time_ns/1e9)})' benchmark-runs/latest_modular_fibonacci_16/summary.json
jq '.spans | to_entries | sort_by(-.value.total_ns) | .[:10]' benchmark-runs/latest_modular_fibonacci_16/summary.json
# Multi-scale sweep (one profile subprocess per run; results in benchmark-runs/modular_timings.csv,
# rendered by scripts/benchmark_summary.py, plot_benchmarks.py, plot_memory_usage.py)
cargo run --release -p jolt-prover --features profiling -- benchmark --min-scale 18 --max-scale 21 --resume
# Per-batch heap snapshots (*.folded in the run directory, exact bytes; totals in summary.json's .heap; rendered by memory.html)
cargo run --release -p jolt-prover --features profiling,allocative -- profile --name fibonacci --format chrome
# jolt-eval telemetry objectives over the same summary (grammar: telemetry:<workload>:<metric>)
cargo run -p jolt-eval --bin measure-objectives -- --objective telemetry:fibonacci:prover_time_s
# Legacy prover
cargo run --release -p jolt-prover-legacy profile --name sha3 --format chrome
# --name options: sha2, sha3, sha2-chain, sha3-chain, fibonacci, btreemap
RUST_LOG=debug cargo run --release --features allocative -p jolt-prover-legacy profile --name sha3 --format chrome
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.
- today Changed · +93 tokens per session 5feb974952b1
- 4d ago First seen · 272 lines · 5,183 tokens per session scan A 0f12d54fe982
jolt CLAUDE.md is an instructions file published in the GitHub repository a16z/jolt (1,022 stars, last pushed today), licensed Apache-2.0. It adds 5,276 tokens to every session, about $0.0264 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
starknet.js AGENTS.md
AGENTS.md instructions for starknet-io/starknet.js, covering agents.md, setup & core commands, verifying your changes (read this before running tests), architecture map (src/) and conventions.
emilia-protocol AGENTS.md
AGENTS.md instructions for emiliaprotocol/emilia-protocol, covering repository instructions for ai agents, required first read, source discipline, context maintenance and verification.
emilia-protocol CLAUDE.md
Claude Code instructions for emiliaprotocol/emilia-protocol, covering emilia protocol - repo guide, required context, critical, build & ship and outbound & claims.
VCVio AGENTS.md
AGENTS.md instructions for Verified-zkEVM/VCVio, covering vcvio — ai agent guide, fast start, attribution, headers, and docstrings, module scopes and what this project is.
emilia-protocol copilot-instructions.md
Copilot instructions for emiliaprotocol/emilia-protocol: Read AGENTS.md and AICONTEXT.md before proposing changes. Current evidence and provenance are in public/.well-known/emilia-context.json. Treat archived, staged, private, and outreach documents as non-authoritative for current behavior or standards status.
emilia-protocol GEMINI.md
Gemini CLI instructions for emiliaprotocol/emilia-protocol: Read AGENTS.md and AICONTEXT.md before analyzing or editing this repository. Use public/.well-known/emilia-context.json for current evidence counts and provenance. Do not infer current behavior or standards status from archived, staged, private, or randomly…