evm-asm: Instructions file for Claude Code

CLAUDE.md

evm-asm CLAUDE.md is an instructions file for Claude Code from Verified-zkEVM/evm-asm. It costs 1,359 tokens per session, scanned A, original, MIT.

Project instructions for Verified-zkEVM/evm-asm, covering planning, proof-first code changes, proof conventions, and module organization. A proof is a machine-checked argument that a program or transformation is correct.

In plain words
What is it for?
Use them when porting guest routines, updating the project plan, checking generated code against deployed bytes, or writing kernel-checked proofs.
Why use it?
They keep implementation and verification work aligned with the project's required proof methods and byte-level compatibility checks.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

This is Verified-zkEVM/evm-asm's own configuration. It tells Claude Code how to work on evm-asm itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything evm-asm configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Verified-zkEVM/evm-asm/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Verified-zkEVM/evm-asm

Made for: Claude Code.

Wrote 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.

agentmods badge for evm-asm CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/verified-zkevm/evm-asm/claude-md.svg)](https://agentmods.dev/instructions/verified-zkevm/evm-asm/claude-md)
Your own site
<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>
Per session 1,359 This file is loaded in full into every session.
When invoked 1,359 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01359 $0.01359
Opus 5 $0.00679 $0.00679
Sonnet 5 $0.00272 $0.00272
Haiku 4.5 $0.00136 $0.00136

Measured 4d ago against content hash d65fa6d180da, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

CLAUDE.md · 45 lines

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 to main. 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_decide or bv_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_decide 206→0, bv_decide 290→0); the trusted base is now only the three classical axioms (propext, Classical.choice, Quot.sound) — with one scoped, documented exception: the release-pinned riscv-zkvm dependency axiomatizes its platform primitives (RiscvZkvm/Sail/RiscvExtras.lean declares 75 axioms — 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 74 EvmAsm.Rv64.SailEquiv.* declarations (the single import RiscvZkvm.Sail.InstsEnd site is EvmAsm/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 in scripts/axiom_baseline.json and audited by lake exe axiomsweep --check.
    • Use instead: decide for concrete decidable propositions (the Lean kernel's Nat is GMP-backed, so decide is fast even on concrete 256-bit BitVec goals); omega/bv_omega for linear (bit)vector arithmetic; simp/ext/BitVec.eq_of_getLsbD_eq for bitvector identities (per-bit getLsbD reasoning, with BitVec.getLsbD_of_ge/getLsbD_add/carry_zero and block-splits). For multi-limb two's-complement, reuse EvmWordArith.add_carry_chain_correct. See PLAN.md ("bv_decide purge") for the full toolkit.
    • CI enforcement (two complementary gates): scripts/check-forbidden-tactics.sh is a fast source scan that fails on any bv_decide/native_decide tactic invocation in EvmAsm/**.lean (prose mentions must be wrapped in `backticks`); scripts/check-axioms.sh is the kernel-truth backstop that runs #print axioms on the witnessed proofs and rejects any non-classical axiom (including sorryAx, Lean.ofReduceBool, Lean.trustCompiler, and bv_decide/native_decide trust axioms). To forbid an additional TCB-expanding tactic, add its token to FORBIDDEN in check-forbidden-tactics.sh. A third, whole-library backstop, lake exe axiomsweep --check (report-only in CI during its initial soak), sweeps every reportable EvmAsm.* declaration (private declarations included; compiler-generated auxiliaries are traversed, surfacing on their parents) — not just the witnessed registry surface — for kernel-level axiom/sorryAx taint against the committed baseline scripts/axiom_baseline.json; after intentionally adding or closing a sorry, run lake exe axiomsweep --update-baseline and commit the diff.

Read the full file on GitHub · 45 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. 4d ago Changed · +3 lines · +53 tokens per session d65fa6d180da
  2. 8d ago First seen · 42 lines · 1,306 tokens per session scan A 93e280d63e38

Subscribe to this mod's changes

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.

Related

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens