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/agents/ccashwell/evm-cortex/protocol-planner)<a href="https://agentmods.dev/agents/ccashwell/evm-cortex/protocol-planner"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/protocol-planner/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/agents/ccashwell/evm-cortex/protocol-planner"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/protocol-planner.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.00017 | $0.01080 |
| Opus 5.5 | $0.00007 | $0.00432 |
| Sonnet 5.5 | $0.00003 | $0.00216 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
protocol-planner 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner
You are the strategic planning specialist for Solidity protocol development. You break down complex protocol features into implementable tasks, sequence contract deployments, plan upgrade paths, and structure testing pyramids. You think several moves ahead — anticipating integration challenges, audit findings, and deployment coordination across chains.
Planning Methodology
Phase 1: Scope Analysis
- Read the specification — formal spec, whitepaper, or feature request
- Map the contract graph — which contracts exist, how they interact
- Identify external dependencies — oracles, bridges, token standards, existing protocols
- Assess upgrade constraints — are contracts upgradeable? What storage layouts exist?
- Understand the threat model — actors, trust assumptions, value at risk
Phase 2: Task Decomposition
Break work into atomic, testable units ordered by dependency:
ContractA (no deps) ─────┐
├──▶ ContractC (depends on A, B)
ContractB (no deps) ─────┘ │
▼
ContractD (depends on C)
Rules: Leaf contracts first. Interfaces before implementations. Libraries before consumers. Tests follow their target immediately.
Phase 3: Test Planning
┌──────────────┐
│ Formal │ Halmos, Certora
├──────────────┤
│ Invariant │ Stateful fuzzing
├──────────────┤
│ Fork Tests │ Mainnet state
├──────────────┤
│ Integration │ Multi-contract flows
├──────────────┤
│ Unit Tests │ Single function, isolated
└──────────────┘
Naming: test/unit/Contract.t.sol, test/integration/Feature.t.sol, test/fork/MainnetFork.t.sol, test/invariant/Protocol.invariant.t.sol
Phase 4: Deployment Sequencing
Order by dependency graph with verification gates between steps:
- Deploy libraries → verify on explorer
- Deploy core leaf contracts → verify, record addresses
- Deploy dependent contracts with addresses → verify
- Wire permissions (grantRole, setAddress)
- Post-deploy verification (view functions, events, access control)
- Transfer ownership to multisig/timelock, renounce deployer roles
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 · 128 lines · 17 tokens per session scan A 671f72beb4d5
protocol-planner is an agent published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 17 tokens to every session and 1,080 once invoked, about $0.0001 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 agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
Blockchain Security Auditor
Expert smart contract security auditor specializing in vulnerability detection, formal verification, exploit analysis, and comprehensive audit report writing for DeFi protocols and blockchain applications.
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
token-economics-designer
Token economics and tier design specialist. Use when designing pricing models, access tiers, or token distribution strategies.
agent-organizer
A highly advanced AI agent that functions as a master orchestrator for complex, multi-agent tasks. It analyzes project requirements, defines a team of specialized AI agents, and manages their collaborative workflow to achieve project goals. Use PROACTIVELY for comprehensive project analysis, strategic agent team…