openzeppelin-expert

An expert guide to OpenZeppelin Contracts v5, a library of reusable Solidity components for Ethereum and other compatible blockchains.

In plain words
What is it for?
Use it when designing Solidity contracts with ownership, roles, account managers, ERC-20, ERC-721, ERC-1155, voting, timelocks, proxies, reentrancy protection, signatures, or Merkle proofs.
Why use it?
It helps developers choose established patterns for access control, token contracts, governance, upgradeability, and cryptographic operations. This reduces the need to design these security-sensitive building blocks from scratch.

Agent

Install

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.

agentmods
npx agentmods add agents/ccashwell/evm-cortex/openzeppelin-expert
Clone the repo
git clone --depth 1 https://github.com/ccashwell/evm-cortex
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,196 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.02196
Opus 5 $0.00009 $0.01098
Sonnet 5 $0.00003 $0.00439
Haiku 4.5 $0.00002 $0.00220

Measured 2d ago against content hash 24d175b3f39a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

agents/openzeppelin-expert.md · 253 lines

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) {}
}

Read the full file on GitHub · 253 lines

Changes

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.

  1. 2d ago First seen · 253 lines · 17 tokens per session scan A 24d175b3f39a

Subscribe to this mod's changes

openzeppelin-expert 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 2,196 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.

Related

Other agents, from other repositories

dispatcher-unification-design

Status: phase-2 design drafted; implementation is held for maintainer review. Load when: working on blockverdict transaction dispatch, or on any "single-tx diverges from multi-tx" false-reject.

Verified-zkEVM/evm-asm · 0 tokens

orquestra-pda-explorer

Derives Program Derived Addresses (PDAs) from known seeds and fetches their on-chain data via Orquestra MCP. Resolves missing accounts iteratively by extracting pubkeys from returned PDA fields. Uses ONLY Orquestra MCP tools. Examples: Context: User needs to find a user's stake account for a specific program user…

berkayoztunc/orquestra · 293 tokens

helius-integration-specialist

Specialist agent for Helius + Solana integrations — queries live blockchain data, sends transactions via Sender, sets up webhooks, streams real-time data, and routes to domain-specific skills for trading, frontend development, and protocol research.

helius-labs/core-ai · 54 tokens

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…

ChainAware/behavioral-prediction-mcp · 247 tokens

chainaware-lending-risk-assessor

Assesses borrower risk for DeFi lending by combining fraud probability, on-chain experience, and risk appetite from ChainAware's Behavioral Prediction MCP. Returns a Borrower Risk Grade (A–F), a recommended collateral ratio, and an interest rate tier — so lending protocols can price risk per wallet rather than…

ChainAware/behavioral-prediction-mcp · 249 tokens

chainaware-sybil-detector

Screens a list of wallet addresses for Sybil attacks, coordinated voting fraud, and low-quality participation in DAO governance votes. Use this agent PROACTIVELY whenever a user wants to validate voter eligibility, detect Sybil wallets in a governance proposal, weight votes by wallet quality, filter low-reputation…

ChainAware/behavioral-prediction-mcp · 171 tokens