What is evmole AGENTS.md?

Project instructions for EVMole, a tool that extracts structured facts from deployed Ethereum Virtual Machine (EVM) bytecode. Bytecode is the low-level program stored on a blockchain.

Use them when changing or testing EVMole itself, including its Rust core, Python, JavaScript, WebAssembly, Go, CLI, or agent components.

They direct contributors to the correct source code and testing areas for the core analyzer, language bindings, command-line tools, and agent integrations.

How cdump/evmole configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to cdump/evmole. 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/cdump/evmole/master/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/cdump/evmole

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/cdump/evmole/agents-md/github.svg)](https://agentmods.dev/instructions/cdump/evmole/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/cdump/evmole/agents-md"><img src="https://agentmods.dev/badge/instructions/cdump/evmole/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/cdump/evmole/agents-md"><img src="https://agentmods.dev/badge/instructions/cdump/evmole/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 607 This file is loaded in full into every session.

When invoked 607 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.

Model	Per session	Once invoked
Fable 5.1	$0.00607	$0.00607
Opus 5.5	$0.00243	$0.00243
Sonnet 5.5	$0.00121	$0.00121
Haiku 4.5	$0.00061	$0.00061

Measured 2mo ago against content hash 8c40f0975d86, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

evmole AGENTS.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 2mo 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.

AGENTS.md · 47 lines

What it actually says

EVMole agent guide

EVMole extracts structured facts from deployed EVM runtime bytecode.

This is the EVMole implementation repository. For requests to implement, debug, refactor, review, or test EVMole itself, inspect and modify the repository source. Do not use the published EVMole packages, MCP server, JSON CLI, or portable skill as a substitute for understanding the implementation. Running locally built libraries, binaries, and adapters for validation is expected.
Treat input as deployed/runtime bytecode. Creation bytecode is not executed or stripped automatically.
Route repository development by component:
- Core analysis algorithms and the public Rust API: src/ and Cargo.toml.
- Python bindings: src/interface_py.rs and python/.
- JavaScript/WASM bindings and the JSON CLI: src/interface_js.rs, src/interface_wasm.rs, and javascript/.
- Go bindings: go/.
- MCP server, shared agent adapter, portable skill, schemas, and agent tests: javascript/src/agent_api.mjs and agent/.
Use agent/skills/evm-bytecode-analysis/SKILL.md only when the user asks to analyze supplied deployed runtime bytecode, or when changing or testing the CLI, MCP server, portable skill, schemas, interpretation behavior, or agent integration.
When helping a separate project integrate EVMole, use the existing binding for the project's language: the evmole Rust crate, evmole JavaScript package, evmole Python package, or github.com/cdump/evmole/go. Start with README.md and the language-specific README.
Reuse the shared agent adapter when changing the CLI, MCP server, skill, or agent tests; do not duplicate its request, response, validation, or pagination logic.
Validate the components changed:
- Rust: cargo fmt --check, cargo test, and cargo clippy --all-features -- -D warnings.
- JavaScript and the agent adapter: build with npm --prefix javascript run build, then run focused tests with npm --prefix javascript test and npm --prefix agent/mcp test.
- Go: build the embedded WASM with make -C go wasm, then run make -C go test.
- Python: build with Maturin and run python3 python/test_python.py; use the release workflow for the supported Python and platform matrix.
When reporting bytecode-analysis results, describe inferred arguments, mutability, and storage information as inferred, not verified source-level facts.
Preserve unrelated benchmark providers, datasets, result directories, and user changes.

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.

2mo ago First seen · 47 lines · 607 tokens per session scan A 8c40f0975d86

Subscribe to this mod's changes

evmole AGENTS.md is an instructions file published in the GitHub repository cdump/evmole (473 stars, last pushed yesterday), licensed MIT. It adds 607 tokens to every session, about $0.0024 per session on Opus 5.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.

Web3 and blockchain bytecode ethereum evm solidity

evmole AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
evmole AGENTS.mdcdump/evmole	Instructions file	473	yesterday	MIT	A	607	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

evmole: Instructions file for Codex