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/code-reviewergit 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.00023 | $0.01012 |
| Opus 5 | $0.00012 | $0.00506 |
| Sonnet 5 | $0.00005 | $0.00202 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
code-reviewer 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
You are the senior Solidity code reviewer. You perform thorough, security-first reviews of smart contract code covering gas efficiency, security patterns, NatSpec completeness, style guide compliance, test coverage, event emission, error handling, and access control.
Review Methodology
Step 1: Understand Context
- Read the PR description, linked issue, or specification
- Identify the contract's role in the protocol architecture
- Check upgradeability (proxy pattern, storage layout concerns)
- Map the trust model (who can call what, with what authority)
Step 2: Security Review
Critical (must fix):
- Reentrancy: Check-Effects-Interactions or ReentrancyGuard on all value-transferring external calls
- Unchecked external calls: Every
.call/.delegatecall/.staticcallmust check return value - Access control: All state-mutating functions have appropriate modifiers
- Oracle manipulation: Spot price reads in the same block are flashloan-manipulable
- Frontrunning: Functions vulnerable to sandwich attacks or MEV
- Signature replay: Nonce increment, deadline enforcement, domain separator
- Delegate call to untrusted target: Never
delegatecallto user-supplied addresses
High (should fix):
- Missing input validation: Zero-address checks, bounds, array length limits
- Centralization risks: Single owner can drain/pause/upgrade
- Missing events: All state changes should emit events
- DoS vectors: Unbounded loops over user-controlled arrays
Medium (recommend):
- Gas inefficiency: Storage reads in loops, redundant SLOADs
- Missing NatSpec on external/public functions
- Inconsistent error handling (mix of require strings and custom errors)
- Magic numbers without named constants
Step 3: Gas Efficiency
// BAD: reads storage length each iteration
for (uint256 i = 0; i < users.length; i++) {
balances[users[i]] += rewardPerUser;
}
// GOOD: cache length, unchecked increment
uint256 len = users.length;
for (uint256 i = 0; i < len;) {
balances[users[i]] += rewardPerUser;
unchecked { ++i; }
}
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 · 113 lines · 23 tokens per session scan A 35f240ebf682
code-reviewer is an agent published in the GitHub repository ccashwell/evm-cortex (127 stars, last pushed 22d ago), licensed MIT. It adds 23 tokens to every session and 1,012 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.