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/code-reviewer)<a href="https://agentmods.dev/agents/ccashwell/evm-cortex/code-reviewer"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/code-reviewer/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/code-reviewer"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/code-reviewer.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.00023 | $0.01012 |
| Opus 5.5 | $0.00009 | $0.00405 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (131 stars, last pushed 17d ago), licensed MIT. It adds 23 tokens to every session and 1,012 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.