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 skills add evmts/tevm --skill zevmgit clone --depth 1 https://github.com/evmts/tevmWrote 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/skills/evmts/tevm/zevm)<a href="https://agentmods.dev/skills/evmts/tevm/zevm"><img src="https://agentmods.dev/badge/skills/evmts/tevm/zevm.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.00061 | $0.01816 |
| Opus 5 | $0.00030 | $0.00908 |
| Sonnet 5 | $0.00012 | $0.00363 |
| Haiku 4.5 | $0.00006 | $0.00182 |
Grade A, and why
zevm 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zevm
Use the Zevm source checkout and its pinned dependencies. Zevm requires Zig 0.15.2.
Choose the right surface
Zevm is a Zig Ethereum execution implementation with three product surfaces:
| Need | Surface |
|---|---|
| Local or forked development RPC | zevm --mode trusted, with Ethereum, Anvil, EVM, and txpool namespaces |
| Proof-verified reads | zevm --mode light or the light-client C ABI |
| Embed execution | Import the zevm Zig module, or link libzevm through zevm.h |
Use Zevm when native code, a standalone JSON-RPC node, proof-backed light reads, block processing, or a C-compatible library is required. Use Tevm when the caller is JavaScript or TypeScript and needs typed Solidity imports and an in-process viem-compatible client.
Build from source
Run from the Zevm repository root:
zig build --fetch
zig build -Doptimize=ReleaseSafe
zig build c-ffi -Doptimize=ReleaseSafe
zig build c-smoke -Doptimize=ReleaseSafe
| Command | Output |
|---|---|
zig build |
zig-out/bin/zevm |
zig build run -- --mode trusted --host 127.0.0.1 --port 8545 |
trusted development JSON-RPC node |
zig build test |
default unit and integration test graph |
zig build c-ffi |
zig-out/lib/libzevm.a, platform shared library, and zig-out/include/zevm.h |
zig build npm-native |
local N-API addon at zig-out/npm/native/zevm.node |
zig build verify-fast |
local release-oriented checks |
Do not replace build.zig.zon dependency URLs with sibling paths. The package pins Voltaire and Guillotine Mini by URL and hash.
Embed the C ABI
The ABI is handle-based and currently exposes the proof-verified light client. Link the shared library in rc builds unless the host build system also supplies the static library's transitive crypto objects.
#include <stdio.h>
#include "zevm.h"
int main(void) {
if (zevm_abi_version() != ZEVM_ABI_VERSION) return 1;
ZevmHandle *handle = zevm_light_init(
ZEVM_NETWORK_MAINNET,
"http://127.0.0.1:0/beacon",
"http://127.0.0.1:0/execution");
if (handle == NULL) return 2;
printf("zevm %s, network=%s, status=%d\n",
zevm_version(),
zevm_light_network_name(ZEVM_NETWORK_MAINNET),
zevm_light_status(handle));
zevm_light_shutdown(handle);
return 0;
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 142 lines · 61 tokens per session scan A 78df90f6e2d4
zevm is a skill published in the GitHub repository evmts/tevm (446 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,816 once invoked, about $0.0003 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-09-07.
Other skills, from other repositories
evm-bytecode-analysis
Analyze supplied deployed EVM runtime bytecode with EVMole or guide a separate application in integrating a published EVMole Rust, Go, Python, or JavaScript binding. Use for unverified-contract inspection, ABI reconstruction from runtime code, selector discovery, storage-access analysis, EVM control-flow inspection…
aomi-build
Scaffold new Aomi apps and plugins from API docs, OpenAPI/Swagger specs, or SDK references. aomi-build generates production-ready Rust SDK crates (lib.rs, client.rs, tool.rs) with tool schemas, preambles, host-interop flows, and validation — turning a vendor's API surface into AI-agent-callable tools. It covers the…
ethereum-development
Production-grade Ethereum/EVM development workflow for smart contracts, dApps, transactions, clients, gas optimization, testing, security review, deployment, verification, monitoring, and incident response across Foundry, Hardhat, Solidity, TypeScript, viem, ethers, wagmi, and common EVM networks.
solidity
Solidity smart-contract authoring authority — ERC20/ERC721/ERC1155 token standards, reentrancy guards, access control, gas optimisation, upgradeable proxies, Foundry testing, fuzzing, invariant checks, and production contract security for EVM chains.
auditing-foundry-smart-contract-security
Pre-deployment security audit of Solidity smart contracts in a Foundry project. Combines static analysis (Slither, Aderyn), symbolic execution (Mythril), and property-based testing (forge fuzz + invariant tests with handlers) to catch reentrancy, access-control, oracle/price manipulation, and arithmetic bugs BEFORE…
solidity-language-docs
Solidity 0.8.36 — smart contracts, types, functions, modifiers, events, inheritance, libraries, assembly, ABI.