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 cdump/evmole --skill evm-bytecode-analysisgit clone --depth 1 https://github.com/cdump/evmoleWrote 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/cdump/evmole/evm-bytecode-analysis)<a href="https://agentmods.dev/skills/cdump/evmole/evm-bytecode-analysis"><img src="https://agentmods.dev/badge/skills/cdump/evmole/evm-bytecode-analysis/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.
<a href="https://agentmods.dev/skills/cdump/evmole/evm-bytecode-analysis"><img src="https://agentmods.dev/badge/skills/cdump/evmole/evm-bytecode-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 46 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00135 | $0.00846 |
| Opus 5.5 | $0.00054 | $0.00338 |
| Sonnet 5.5 | $0.00027 | $0.00169 |
| Haiku 4.5 | $0.00014 | $0.00085 |
Grade A, and why
evm-bytecode-analysis 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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EVM Bytecode Analysis
Use EVMole for deterministic, local extraction from deployed EVM runtime bytecode.
Route by intent
- To answer a question from supplied runtime bytecode, use the analysis workflow below. Prefer the MCP tool when available and otherwise use the JSON CLI.
- To add published EVMole to a separate application's code, use the native library for the project's language instead of invoking the MCP server or agent JSON adapter from product code. Read references/libraries.md for package names, entry points, and documentation.
- To implement, debug, refactor, or review EVMole itself, follow that repository's contributor instructions and inspect its source. Do not use a published package, MCP server, or JSON CLI as a substitute for understanding the implementation. Read this skill only when the repository task targets the CLI, MCP server, agent adapter, schemas, interpretation behavior, or the skill itself.
- Use the JSON CLI as an application process boundary only when the user explicitly wants a subprocess or a language without a supported binding.
Workflow
-
Obtain or confirm deployed runtime bytecode. Treat an address as an address, not bytecode; ask for the runtime code or use another authorized RPC tool to fetch it. Do not ask EVMole to execute or strip creation bytecode.
-
Select only the features needed:
selectorsfor function selectors and dispatch locations.argumentsfor inferred argument lists; this implies selectors.stateMutabilityfor inferred mutability; this implies selectors.storageortransientStoragefor inferred storage access.metadatafor terminal compiler metadata.disassembly,basicBlocks, orcontrolFlowGraphfor instruction and control-flow evidence.
-
Prefer the
analyze_evm_bytecodeMCP tool when available. Otherwise run the JSON CLI:npx -y evmole@latest analyze --bytecode 0x... --include selectors,arguments,stateMutability,storage
What ships with it
5 files 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.
- 1mo ago First seen · 72 lines · 135 tokens per session scan A 0bc7c6eb5437
evm-bytecode-analysis is a skill published in the GitHub repository cdump/evmole (471 stars, last pushed 3d ago), licensed MIT. It adds 135 tokens to every session and 846 once invoked, about $0.0005 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.
Other skills, from other repositories
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-language-docs
Solidity 0.8.36 — smart contracts, types, functions, modifiers, events, inheritance, libraries, assembly, ABI.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
solidity-coding
Write and modify production Solidity contracts in Foundry projects. Use when writing a contract, implementing a function, adding errors, events, or structs, designing contract architecture, optimizing gas, hardening security, planning upgrades, or working in src/.
foundry-testing
Write and debug Foundry tests and Solidity scripts. Use when writing unit, fuzz, fork, or invariant tests, writing bulloak BTT .tree specs (Branching Tree Technique), using cheatcodes, benchmarking gas, measuring coverage, writing deploy scripts, or working in tests/ or script/.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.