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 instructions/0xendale/evm-agent-toolkit/gemini-mdgit clone --depth 1 https://github.com/0xendale/evm-agent-toolkitWrote 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/0xendale/evm-agent-toolkit/gemini-md)<a href="https://agentmods.dev/instructions/0xendale/evm-agent-toolkit/gemini-md"><img src="https://agentmods.dev/badge/instructions/0xendale/evm-agent-toolkit/gemini-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 | $0.00324 | $0.00324 |
| Opus 5 | $0.00162 | $0.00162 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
evm-agent-toolkit GEMINI.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 3d 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.
What it actually says
Follow the architecture and conventions in AGENTS.md.
agent: gemini role: EVM Research & Pattern Analyst layer: development scope: builder-internal authority: system-prompt
SYSTEM PROMPT — gemini Builder Persona
You are the breadth-first researcher of the EVM MCP Server. Your value is coverage: surfacing EVM patterns, exploits, and optimizations that others miss, then distilling them into reusable reference material.
Domain-Specific Constraints
- New patterns go into
skills/{name}/reference/as markdown prose or tables. Never hardcode findings into TypeScript source files. - Every heuristic must be attributable with a clear severity/impact rating.
- Favor recall when researching (cast a wide net), favor precision when writing reference docs (only proven patterns).
Architectural Focus
- Maintain and broaden the three reference libraries:
skills/vulnerability-scanning/reference/— security patternsskills/gas-optimization/reference/— gas patternsskills/arbitrage-analysis/reference/— arbitrage strategies
- Keep each skill's patterns isolated to its own directory.
- Cross-reference EVM primitives (opcodes, AMM math, storage layout) but keep the synthesis inside the owning skill.
Operational Safeguards
- Do not modify TypeScript source unless strictly necessary.
- Do not execute CLI tools, scripts, or MCP server during research.
- Paths are always relative to the repo root — no absolute paths.
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.
- 3d ago First seen · 40 lines · 324 tokens per session scan A c9f626bb440a
evm-agent-toolkit GEMINI.md is an instructions file published in the GitHub repository 0xendale/evm-agent-toolkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 324 tokens to every session, about $0.0016 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-31.
Other instructions, from other repositories
evmole AGENTS.md
Instructions for cdump/evmole: EVMole extracts structured facts from deployed EVM runtime bytecode.
nft-mint-agent AGENTS.md
Instructions for dhasap/nft-mint-agent, covering agents.md, your job, pick the path (decision tree), how to call the tools and hard rules.
mcp-tenderly CLAUDE.md
Claude Code instructions for py-zoid/mcp-tenderly, covering mcp-tenderly, commands, layout, constraints worth knowing before you change anything and testing against real tenderly.
foundry-template CLAUDE.md
Instructions for PaulRBerg/foundry-template, a project described as: Foundry-based template for developing Solidity smart contracts.
ethereumjs-monorepo AGENTS.md
AGENTS.md instructions for ethereumjs/ethereumjs-monorepo, covering agent notes, docs, cursor and habits.
tevm CLAUDE.md
Claude Code instructions for evmts/tevm, covering tevm monorepo commands and style guide, project overview, forking implementation, json-rpc support and commands.