Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ccashwell/evm-cortexnpx agentmods add skills/ccashwell/evm-cortex/l2-deploymentWrote 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/ccashwell/evm-cortex/l2-deployment)<a href="https://agentmods.dev/skills/ccashwell/evm-cortex/l2-deployment"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/l2-deployment.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.00048 | $0.01848 |
| Opus 5 | $0.00024 | $0.00924 |
| Sonnet 5 | $0.00010 | $0.00370 |
| Haiku 4.5 | $0.00005 | $0.00185 |
Grade A, and why
l2-deployment 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.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
L2 Deployment Patterns
L2 Gas Economics
L2 transaction cost = L2 execution gas + L1 data posting cost
| Operation | L1 (Ethereum) | L2 (Base/OP/Arb) | Savings |
|---|---|---|---|
| ETH transfer | ~$0.50 | ~$0.0003 | 99.9% |
| ERC-20 transfer | ~$2.00 | ~$0.001 | 99.9% |
| Uniswap swap | ~$8.00 | ~$0.002-0.003 | 99.9% |
| NFT mint | ~$5.00 | ~$0.002 | 99.9% |
| Contract deploy | ~$50-500 | ~$0.05-0.50 | 99% |
Post-EIP-4844 (blobs), L1 data costs dropped 10-100x for L2s.
L2-Specific Considerations
PUSH0 Opcode Compatibility
PUSH0 was introduced in the Shanghai upgrade (EVM version). Some L2s may lag behind on EVM version support:
# foundry.toml — set EVM version explicitly for L2
[profile.default]
evm_version = "cancun" # Base, Optimism, Arbitrum all support cancun
# If targeting an L2 that doesn't support cancun:
# evm_version = "paris" # No PUSH0
Block Time Differences
| Chain | Block Time | Implication |
|---|---|---|
| Ethereum | ~12s | Standard |
| Base | 2s | Faster confirmations |
| Optimism | 2s | Faster confirmations |
| Arbitrum | ~0.25s | Near-instant |
Avoid hardcoding time assumptions based on block numbers.
L2-Specific Addresses
// Optimism / Base predeploys (same addresses on all OP Stack chains)
address constant L2_CROSS_DOMAIN_MESSENGER = 0x4200000000000000000000000000000000000007;
address constant L2_STANDARD_BRIDGE = 0x4200000000000000000000000000000000000010;
address constant L2_TO_L1_MESSAGE_PASSER = 0x4200000000000000000000000000000000000016;
address constant WETH = 0x4200000000000000000000000000000000000006;
address constant L1_BLOCK = 0x4200000000000000000000000000000000000015;
address constant GAS_PRICE_ORACLE = 0x420000000000000000000000000000000000000F;
// Arbitrum system addresses
address constant ARB_SYS = 0x0000000000000000000000000000000000000064;
address constant ARB_RETRYABLE_TX = 0x000000000000000000000000000000000000006E;
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 · 207 lines · 48 tokens per session scan A de722580c873
l2-deployment is a skill published in the GitHub repository ccashwell/evm-cortex (127 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,848 once invoked, about $0.0002 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-03.
Other skills, from other repositories
cli-anything-eth2-quickstart
Use eth2-quickstart to autonomously deploy a hardened Ethereum node, install execution and consensus clients, configure validator metadata, expose RPC safely, and inspect node health with structured JSON output.
devloop
Goal-driven development loop — define objective, write rules with key-results, verify visually, sync to issue tracker.
skill0
Root index of x-cmd skill0 sub-skills. Defines the OKR-style agent workflow (goal → rule-verified results → execute), skill discovery, and agent tooling preferences. Style: principle-first, concise, delegate specifics to authoritative external sources.
bitcoin-core-operations
Running Bitcoin Core in production: bitcoin.conf reference, sections, pruning, signet, dbcache, mempool tuning, network bind, Tor, IBD considerations, debug.log analysis. USE WHEN: deploying a node, tuning performance, debugging IBD issues, configuring multi-network nodes.
blockchain-infrastructure
Use this skill when asked about blockchain node deployment, RPC infrastructure, CI/CD for smart contracts, monitoring and alerting for blockchain networks, MEV infrastructure (Flashbots, builders, relays), key management (KMS, HSM), and environment management for devnet/testnet/staging/mainnet. Languages: Go, Rust…
Frontend Playbook
Complete build-to-production pipeline for Ethereum dApps — fork mode setup, IPFS deployment, Vercel config, ENS subdomain setup, and a full production checklist built around Scaffold-ETH 2.