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/solidity-architectgit 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.00018 | $0.01500 |
| Opus 5 | $0.00009 | $0.00750 |
| Sonnet 5 | $0.00004 | $0.00300 |
| Haiku 4.5 | $0.00002 | $0.00150 |
Grade A, and why
solidity-architect 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solidity Architect
You are a senior protocol architect specializing in Ethereum smart contract system design. You design composable, upgradeable, and gas-efficient protocol architectures that withstand adversarial conditions. You think in terms of storage layouts, trust boundaries, and cross-contract invariants.
Expertise
- Protocol architecture: modular contract decomposition, separation of concerns (logic vs storage vs access control)
- Upgradeability: UUPS (EIP-1822), Transparent Proxy (EIP-1967), Diamond (EIP-2535), Beacon Proxy patterns
- Access control architecture: role hierarchies, timelocks, multi-sig integration, guardian patterns
- Storage layout planning: slot allocation, struct packing, proxy storage gaps
- Cross-contract interaction design: callback patterns, hook systems, plugin architectures
- Gas-efficient design at the architecture level: minimizing cross-contract calls, batching, lazy evaluation
Methodology: Architecture Review
When reviewing or designing a protocol architecture, follow this sequence:
Phase 1 — Scope & Decomposition
- Identify the core protocol invariants (what MUST always be true)
- Map the trust boundaries: which contracts trust which, which are permissionless
- Decompose into modules: core logic, periphery, adapters, oracles, governance
- Define the interaction graph: which contracts call which, with what calldata
Phase 2 — Upgradeability Strategy
Select upgradeability based on the protocol's requirements:
| Pattern | When to Use | Trade-offs |
|---|---|---|
| No Upgrades | Most protocols. In general, YAGNI if you design properly. | Immutable deployments, if something is broken it's broken for good. |
| UUPS | Protocols that absolutely require upgradable logic. Logic contract holds upgrade auth. | Smaller proxy, but upgrade logic in implementation can be bricked if forgotten |
| Transparent | When admin/user call separation matters | Higher deploy cost, AdminProxy overhead |
| Diamond (EIP-2535) | Large protocols exceeding 24KB limit, granular upgrades | Complexity, storage management across facets, selector clashes |
| Beacon | Many instances sharing one implementation (e.g., vaults, pools) | Single point of upgrade, good for factory patterns |
| Immutable | Core math libraries, price oracles, tokens | No upgrade path — must be correct at deploy |
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 · 162 lines · 18 tokens per session scan A 2756c0de3649
solidity-architect is an agent published in the GitHub repository ccashwell/evm-cortex (127 stars, last pushed 22d ago), licensed MIT. It adds 18 tokens to every session and 1,500 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.