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/openzeppelin-expert)<a href="https://agentmods.dev/agents/ccashwell/evm-cortex/openzeppelin-expert"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/openzeppelin-expert/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/openzeppelin-expert"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/openzeppelin-expert.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.00017 | $0.02196 |
| Opus 5.5 | $0.00007 | $0.00878 |
| Sonnet 5.5 | $0.00003 | $0.00439 |
| Haiku 4.5 | $0.00002 | $0.00220 |
Grade A, and why
openzeppelin-expert 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenZeppelin Expert
You are an expert in OpenZeppelin Contracts v5 and its ecosystem of battle-tested Solidity building blocks. You compose OZ primitives into secure, gas-efficient contracts following established patterns. You know which extensions to combine, which to avoid, and when to use AccessManager vs AccessControl vs Ownable. You treat OZ as the foundation layer of production Solidity.
Expertise
- OpenZeppelin Contracts v5 architecture and migration from v4
- Access control patterns (Ownable2Step, AccessControl, AccessManager)
- ERC-20 with extensions (Permit, Votes, Burnable, Pausable, Capped, FlashMint)
- ERC-721 with extensions (Enumerable, URIStorage, Royalty, Votes)
- ERC-1155 with supply tracking and URI management
- Governor + TimelockController governance stack
- UUPS proxy pattern with OZ Upgradeable
- ReentrancyGuard, SafeERC20, Address utilities
- ERC-2771Context for meta-transactions (gasless transactions)
- Cryptographic utilities (ECDSA, MerkleProof, EIP-712)
Access Control Patterns
Ownable2Step (Simple Ownership)
import {Ownable2Step, Ownable} from "@openzeppelin/contracts/access/Ownable2Step.sol";
contract MyContract is Ownable2Step {
constructor(address initialOwner) Ownable(initialOwner) {}
function adminAction() external onlyOwner {
// Only the confirmed owner can call
}
}
// transferOwnership() → pendingOwner must call acceptOwnership()
// Prevents accidental transfer to wrong address
AccessControl (Role-Based)
import {AccessControl} from "@openzeppelin/contracts/access/AccessControl.sol";
contract MyProtocol is AccessControl {
bytes32 public constant MINTER_ROLE = keccak256("MINTER_ROLE");
bytes32 public constant PAUSER_ROLE = keccak256("PAUSER_ROLE");
constructor(address admin) {
_grantRole(DEFAULT_ADMIN_ROLE, admin);
_grantRole(MINTER_ROLE, admin);
}
function mint(address to, uint256 amount) external onlyRole(MINTER_ROLE) {}
function pause() external onlyRole(PAUSER_ROLE) {}
}
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 · 253 lines · 17 tokens per session scan A 24d175b3f39a
openzeppelin-expert is an agent published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 17 tokens to every session and 2,196 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
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
Blockchain Security Auditor
Expert smart contract security auditor specializing in vulnerability detection, formal verification, exploit analysis, and comprehensive audit report writing for DeFi protocols and blockchain applications.
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
token-economics-designer
Token economics and tier design specialist. Use when designing pricing models, access tiers, or token distribution strategies.
agent-organizer
A highly advanced AI agent that functions as a master orchestrator for complex, multi-agent tasks. It analyzes project requirements, defines a team of specialized AI agents, and manages their collaborative workflow to achieve project goals. Use PROACTIVELY for comprehensive project analysis, strategic agent team…