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 agents/verified-zkevm/evm-asm/stateless-input-contractgit 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/agents/verified-zkevm/evm-asm/stateless-input-contract)<a href="https://agentmods.dev/agents/verified-zkevm/evm-asm/stateless-input-contract"><img src="https://agentmods.dev/badge/agents/verified-zkevm/evm-asm/stateless-input-contract.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.00000 | $0.00995 |
| Opus 5 | $0.00000 | $0.00498 |
| Sonnet 5 | $0.00000 | $0.00199 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
stateless-input-contract 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stateless Guest Input Contract
This note is for changes to stateless_guest, the EEST converter, and any
RISC-V code that reads the stateless payload. The invariant is simple: the zkVM
guest must consume the same stateless input content as execution-specs
run_stateless_guest.
Source Of Truth
Execution-specs Amsterdam consumes a schema-prefixed SSZ byte string:
execution-specs/src/ethereum/forks/amsterdam/stateless_guest.pyrun_stateless_guest(input_bytes)callsdeserialize_stateless_input, thenverify_stateless_new_payload.execution-specs/src/ethereum/forks/amsterdam/stateless_guest.pydeserialize_stateless_inputrequires the two-byte big-endian schema id0x1501, decodes the remaining bytes asSszStatelessInput, and converts it withssz_to_stateless_input.execution-specs/src/ethereum/forks/amsterdam/stateless_ssz.pydefinesSszStatelessInputas:new_payload_request,witness,chain_config, andpublic_keys.
The zkVM input may have a host-transport wrapper, but the payload behind that
wrapper must be those same schema-prefixed SSZ bytes. Today ziskemu input files
use the host layout from scripts/stateless-gen-input.py and
scripts/eest-stateless-to-input.py:
u64_le payload_len || schema_prefixed_stateless_input || zero padding to 8 bytes
The leading u64_le payload_len and trailing alignment padding are ziskemu host
transport, not execution-specs input content. The guest-visible stateless
payload starts at the bytes counted by that length.
EEST Fixture Conversion
EEST zkevm fixtures already carry execution-specs-compatible fields in each block:
statelessInputBytes: schema-prefixed SSZStatelessInput.statelessOutputBytes: canonical SSZStatelessValidationResult.
scripts/eest-stateless-to-input.py must preserve statelessInputBytes
byte-for-byte when packing ziskemu inputs. It may derive manifest metadata such
as input_len, succ_bit, block_gas_limit, labels, and fixture paths for
scheduling/reporting, but those derived manifest columns are not extra guest
runtime content.
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 First seen · 92 lines · 0 tokens per session scan A cd19f42201c0
stateless-input-contract is an agent published in the GitHub repository Verified-zkEVM/evm-asm (55 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 995 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.