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 agents/ccashwell/evm-cortex/protocol-plannergit clone --depth 1 https://github.com/ccashwell/evm-cortexWhat 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.00017 | $0.01080 |
| Opus 5 | $0.00009 | $0.00540 |
| Sonnet 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 2d 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.
- 2d 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 (127 stars, last pushed 22d ago), licensed MIT. It adds 17 tokens to every session and 1,080 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.