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.
git clone --depth 1 https://github.com/ccashwell/evm-cortexWrote 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/rules/ccashwell/evm-cortex/general)<a href="https://agentmods.dev/rules/ccashwell/evm-cortex/general"><img src="https://agentmods.dev/badge/rules/ccashwell/evm-cortex/general/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/rules/ccashwell/evm-cortex/general"><img src="https://agentmods.dev/badge/rules/ccashwell/evm-cortex/general.svg" alt="Reviewed on agentmods" width="80" 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.00521 | $0.00521 |
| Opus 5.5 | $0.00208 | $0.00208 |
| Sonnet 5.5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
general 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EVM Cortex - Ethereum Protocol Engineering Standards
You are part of EVM Cortex, an Ethereum protocol engineering squad with specialized agents, skills, hooks, and rules.
Solidity Standards
Code Style
- Custom errors over require strings (gas + clarity)
- Named imports:
import {ERC20} from "@openzeppelin/..." - NatSpec on ALL public/external functions
- Constants: UPPER_SNAKE_CASE. Immutables: camelCase or UPPER_SNAKE_CASE
- Events: PascalCase past tense (Deposited, Transferred)
- Max 400 lines per contract file. Extract libraries for reuse.
- Functions under 50 lines. No more than 4 levels of nesting.
Security
- Checks-effects-interactions pattern on all state-changing functions
- ReentrancyGuard on functions with external calls
- SafeERC20 for ALL token transfers
- Ownable2Step over Ownable
- Input validation at all entry points
- USDC has 6 decimals. USDT does not return bool. Use SafeERC20.
- Never hardcode private keys or API keys
- Never trust tx.origin for authorization
Gas Awareness
- Storage packing: fit variables into 32-byte slots
- Prefer calldata over memory for read-only parameters
- Use immutable/constant for values set once
- Cache storage reads in memory when accessed multiple times
- Use unchecked only when overflow is mathematically impossible
Testing (Foundry)
- TDD: write test first, implement, then optimize
- Test naming: test_Function_Condition_Result, test_RevertWhen_Condition
- Fuzz test all math operations
- Fork-test all external protocol integrations
- Gas snapshots:
forge snapshotto track regressions - Target 90%+ coverage on security-critical paths
Conventions
- Say "onchain" not "on-chain"
- Never hallucinate contract addresses -- verify with
cast code - Foundry is the default toolchain (not Hardhat)
- OpenZeppelin Contracts v5 as the standard library
Git Conventions
- Commit format:
<type>: <description> - Types: feat, fix, refactor, docs, test, chore, perf, ci, audit
- Keep commits atomic and focused
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 · 61 lines · 521 tokens per session scan A 1519f14aabb7
general is a cursor rule published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 521 tokens to every session, about $0.0021 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 cursor rules, from other repositories
solana-integration-constraints
Constraints and requirements for Solana integration with MetaMask Connect — wallet adapter config, CAIP-2 IDs, network support per platform, RPC routing, and platform limitations.
zama-protocol-zama-solidity--setups-foundry
Detailed reference for foundry (zama-solidity skill).
cardano-mcp
These rules complement our main development collaboration rules, focusing specifically on the Model Context Protocol (MCP) server project with TypeScript. This project serves as a specialized RAG (Retrieval-Augmented Generation) gateway to existing Cardano resources, documentation, and tools to assist with dApp…
elizaos_v2_onchain_plugins
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐ │ Wallet Provider│ │ Connection Mgmt │ │ Transaction Svc │ │ - Private Keys │───▶│ - RPC Endpoints │───▶│ - Tx Construction│ │ - Public Keys │ │ - Network Config │ │ - Fee Estimation│ │ - Signatures │ │ - Health Check │ │ - Broadcasting │ └─────────────────┘…
solana_core_architecture
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐ │ Entry Point │ │ Instruction │ │ Account │ │ lib.rs │───▶│ Processing │───▶│ Validation │ │ │ │ │ │ │ │ - entrypoint! │ │ - Route dispatch │ │ - Owner checks │ │ - processinst │ │ - Deserialize │ │ - Data validate │.
stacks-development
Guidelines for Stacks blockchain development.