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 skills/obolnetwork/obol-stack/ethereum-networksnpx skills add ObolNetwork/obol-stack --skill ethereum-networksgit clone --depth 1 https://github.com/ObolNetwork/obol-stackWrote 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/obolnetwork/obol-stack/ethereum-networks)<a href="https://agentmods.dev/skills/obolnetwork/obol-stack/ethereum-networks"><img src="https://agentmods.dev/badge/skills/obolnetwork/obol-stack/ethereum-networks.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.00056 | $0.03182 |
| Opus 5 | $0.00028 | $0.01591 |
| Sonnet 5 | $0.00011 | $0.00636 |
| Haiku 4.5 | $0.00006 | $0.00318 |
Grade C, and why
ethereum-networks scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s http://erpc.erpc.svc.cluster.local/ | python3 -m json.tool Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://erpc.erpc.svc.cluster.local/ | python3 -m json.tool How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ethereum Networks
Query Ethereum blockchain data through the local eRPC gateway. Supports any JSON-RPC method, multiple networks, and ERC-20 token lookups.
When to Use
- Block numbers, balances, gas prices, chain IDs
- Transaction lookups and receipts
- Smart contract reads (eth_call)
- Token balance and info queries
- Any
eth_*,net_*, orweb3_*method
When NOT to Use
- Sending transactions, signing, or deploying contracts — use
ethereum-local-wallet - Validator monitoring — use
distributed-validators - Kubernetes pod diagnostics — use
obol-stack
RPC Gateway
The eRPC gateway routes to whichever Ethereum networks are installed:
http://erpc.erpc.svc.cluster.local/rpc/{network}
mainnet is always available. Other networks (e.g. hoodi, arbitrum, robinhood) are available if installed. You can also use evm/{chainId} (e.g. evm/560048 for Hoodi, evm/42161 for Arbitrum One, evm/4663 for Robinhood Chain).
arbitrum and robinhood require the stack operator to have registered an eRPC upstream under that alias (obol network add — ChainList has both). If /rpc/arbitrum or /rpc/robinhood returns 404, the upstream isn't registered — ask the operator.
To see which networks are connected:
curl -s http://erpc.erpc.svc.cluster.local/ | python3 -m json.tool
Write Transactions: Protected Routing & Revert Protection
When a signed tx is broadcast (via ethereum-local-wallet's send-tx, or
directly via eth_sendRawTransaction), eRPC pins the call to Obol's protected
upstream — obol-rpc-mainnet for chain 1, obol-rpc-base for chain 8453. Read
methods still fan out across all configured upstreams; only writes are pinned.
Two consequences worth knowing:
- No front-running on the way to the mempool. Writes don't hit a public transaction pool first, so searchers cannot reorder them around your trade.
- Revert protection is on. The protected upstream refuses to include transactions that would revert at the head block. This saves callers from wasting gas on a guaranteed failure, but it also means a "transaction that vanished" may simply have been rejected upstream as known-to-revert.
What ships with it
4 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.
- 4d ago First seen · 265 lines · 56 tokens per session scan C 1581dc82c1c4
ethereum-networks is a skill published in the GitHub repository ObolNetwork/obol-stack (11 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 3,182 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
kurtosis-ethereum
Run Ethereum multi-client devnets using Kurtosis and the ethpandaops/ethereum-package. Use for spinning up local devnets, syncing public testnets, validating cross-client interop, testing fork transitions, shadowforks, running assertoor checks, debugging CL/EL client interactions, or verifying new feature…
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.
Web3 & Blockchain Development
Production-grade Web3 development with Solidity smart contracts, ethers.js/web3.js integration, DApp architecture, security patterns, and AI-enhanced blockchain development (ChatWeb3, Aider + Gemini 2024).
gen-relationship
Create and refine schema-backed Meshery relationship definitions (models//relationships/.json). Use for "add a relationship", "fix this relationship JSON", classifying kind/type/subType, or reviewing selectors and mutatorRef/mutatedRef patches between model components.
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.
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.