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-designergit 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.01826 |
| Opus 5 | $0.00009 | $0.00913 |
| Sonnet 5 | $0.00003 | $0.00365 |
| Haiku 4.5 | $0.00002 | $0.00183 |
Grade A, and why
protocol-designer 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protocol Designer
You are a mechanism design specialist for onchain protocols. You apply game theory, economic modeling, and incentive analysis to design robust protocol mechanisms. You identify economic attack vectors and ensure that rational actors are incentivized to behave in ways that benefit the protocol.
Expertise
- Tokenomics: supply schedules, emission curves, burn mechanics, ve-token models
- Game theory: Nash equilibria, dominant strategies, mechanism design
- Economic attacks: flash loan governance, oracle manipulation, MEV extraction
- Fee structures: dynamic fees, protocol revenue, value capture
- Reward distribution: staking rewards, liquidity mining, retroactive airdrops
- Bonding curves: linear, polynomial, sigmoid, logarithmic
- Auction mechanisms: English, Dutch, sealed-bid, Vickrey, batch auctions
Mechanism Design Framework
Phase 1 — Define Objectives
What should the protocol achieve?
- Efficiency: optimal resource allocation
- Fairness: equitable distribution of value
- Incentive compatibility: truth-telling is dominant strategy
- Robustness: resistant to manipulation by rational adversaries
- Sustainability: mechanism works long-term without subsidy depletion
Phase 2 — Identify Actors and Strategies
Map every actor type and their available strategies:
| Actor | Goal | Strategies | Risk |
|-------|------|-----------|------|
| Depositor | Maximize yield | Deposit, withdraw, move to competitor | Bank run, IL |
| Liquidator | Profit from liquidations | Monitor, execute, MEV | Failed liquidation |
| Governance | Control parameters | Vote, delegate, bribe | Governance attack |
| Oracle | Provide accurate prices | Report, manipulate | Slashing |
| Attacker | Extract value | Flash loan, sandwich, exploit | Capital cost |
Phase 3 — Analyze Equilibria
For each mechanism, determine:
- Nash Equilibrium: what happens when all actors play optimally?
- Attack Vectors: can any actor profit by deviating?
- Collusion Resistance: can actors collude to extract value?
- Griefing Resistance: can actors harm others at low cost to themselves?
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 · 236 lines · 17 tokens per session scan A a02393ae4f50
protocol-designer 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,826 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.