Borrowing it
Nothing to install: this file belongs to Verified-zkEVM/evm-asm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Verified-zkEVM/evm-asm/main/CLAUDE.mdgit clone --depth 1 https://github.com/Verified-zkEVM/evm-asmWrote 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/verified-zkevm/evm-asm/claude-md)<a href="https://agentmods.dev/instructions/verified-zkevm/evm-asm/claude-md"><img src="https://agentmods.dev/badge/instructions/verified-zkevm/evm-asm/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.1 | $0.01359 | $0.01359 |
| Opus 5 | $0.00679 | $0.00679 |
| Sonnet 5 | $0.00272 | $0.00272 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade A, and why
evm-asm 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 4d 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.
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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
See AGENTS.md for full project context, build instructions, and coding patterns.
PLAN.md Maintenance
Read PLAN.md at the start of each session. Keep it updated as you work:
- Completed a task/opcode: Move it to Done, update the status table and counts
- Discovered new sub-tasks or blockers: Add them to the relevant phase
- Added new infrastructure: Update the Infrastructure section
- Before committing: Check if PLAN.md needs updates for the work in this session
- Progress cockpit (
docs/index.html): not a PLAN.md-class hand update. Counts are generated (scripts/progress-cockpit.sh) and published by CI on merge tomain. Do not copy registry numbers into the HTML.
Proof-first (DCode) ports
To port another guest routine to the proof-first paradigm (code
generated from a separation-logic derivation, byte-identical to the
deployed bytes), follow docs/dcode-porting-playbook.md
end to end — shape selection, proof idioms, the byte gate
(scripts/check-byte-identity.sh), and the remaining-routine ledger
live there. The paradigm itself is documented in docs/sasm-deriv.md.
Proof Conventions
- No
native_decideorbv_decide(or any TCB-expanding tactic): All proofs must be kernel-checkable. Both tactics seal their result behind a native-compiler trust axiom (Lean.ofReduceBool/Lean.trustCompiler) instead of a kernel-checked proof term, introducing a soundness gap. Both have been fully eliminated (native_decide206→0,bv_decide290→0); the trusted base is now only the three classical axioms (propext,Classical.choice,Quot.sound) — with one scoped, documented exception: the release-pinnedriscv-zkvmdependency axiomatizes its platform primitives (RiscvZkvm/Sail/RiscvExtras.leandeclares 75axioms — terminal I/O, reservations, softfloat hooks). Exactly four reach EvmAsm (sys_enable_experimental_extensions,plat_term_write,load_reservation,match_reservation), and only on the Sail-correspondence surface: the 74EvmAsm.Rv64.SailEquiv.*declarations (the singleimport RiscvZkvm.Sail.InstsEndsite isEvmAsm/Rv64/SailEquiv/StateRel.lean). All four are non-Prop uninterpreted constants of inhabited types — no proposition is assumed, consistency is unaffected, and the SailEquiv theorems are effectively parametric over the platform hooks. Any proof that does not touch the Sail layer carries none of these axioms; the per-declaration accounting is pinned inscripts/axiom_baseline.jsonand audited bylake exe axiomsweep --check.- Use instead:
decidefor concrete decidable propositions (the Lean kernel'sNatis GMP-backed, sodecideis fast even on concrete 256-bitBitVecgoals);omega/bv_omegafor linear (bit)vector arithmetic;simp/ext/BitVec.eq_of_getLsbD_eqfor bitvector identities (per-bitgetLsbDreasoning, withBitVec.getLsbD_of_ge/getLsbD_add/carry_zeroand block-splits). For multi-limb two's-complement, reuseEvmWordArith.add_carry_chain_correct. SeePLAN.md("bv_decidepurge") for the full toolkit. - CI enforcement (two complementary gates):
scripts/check-forbidden-tactics.shis a fast source scan that fails on anybv_decide/native_decidetactic invocation inEvmAsm/**.lean(prose mentions must be wrapped in`backticks`);scripts/check-axioms.shis the kernel-truth backstop that runs#print axiomson the witnessed proofs and rejects any non-classical axiom (includingsorryAx,Lean.ofReduceBool,Lean.trustCompiler, andbv_decide/native_decidetrust axioms). To forbid an additional TCB-expanding tactic, add its token toFORBIDDENincheck-forbidden-tactics.sh. A third, whole-library backstop,lake exe axiomsweep --check(report-only in CI during its initial soak), sweeps every reportableEvmAsm.*declaration (private declarations included; compiler-generated auxiliaries are traversed, surfacing on their parents) — not just the witnessed registry surface — for kernel-level axiom/sorryAxtaint against the committed baselinescripts/axiom_baseline.json; after intentionally adding or closing asorry, runlake exe axiomsweep --update-baselineand commit the diff.
- Use instead:
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.
- 4d ago Changed · +3 lines · +53 tokens per session d65fa6d180da
- 8d ago First seen · 42 lines · 1,306 tokens per session scan A 93e280d63e38
evm-asm CLAUDE.md is an instructions file published in the GitHub repository Verified-zkEVM/evm-asm (55 stars, last pushed today), licensed MIT. It adds 1,359 tokens to every session, about $0.0068 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
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
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.