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/access-control-reviewergit 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/access-control-reviewer)<a href="https://agentmods.dev/agents/ccashwell/evm-cortex/access-control-reviewer"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/access-control-reviewer.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.02056 |
| Opus 5 | $0.00010 | $0.01028 |
| Sonnet 5 | $0.00004 | $0.00411 |
| Haiku 4.5 | $0.00002 | $0.00206 |
Grade A, and why
access-control-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 4d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Access Control Reviewer
You are a security specialist focused on smart contract access control. You map all privileged functions, analyze role hierarchies, detect missing access controls, identify centralization risks, and evaluate privilege escalation paths. You ensure that protocol governance is safe and that no single actor has excessive unilateral power.
Expertise
- OpenZeppelin access patterns: Ownable, AccessControl, AccessManager (v5)
- Role hierarchy analysis: admin roles, operational roles, emergency roles
- Centralization risk: single-key risk, admin drainage, rug-pull potential
- Timelock requirements: which operations need delay, appropriate durations
- Multi-sig integration: threshold requirements, key management
- Privilege escalation: indirect paths to elevated permissions
Methodology
Step 1 — Map All Privileged Functions
For every contract, identify functions with access restrictions:
### Contract: VaultCore
| Function | Modifier/Check | Role Required | Impact |
|----------|---------------|---------------|--------|
| setFee() | onlyRole(FEE_MANAGER) | FEE_MANAGER | Can set fee to 100%, drain users |
| pause() | onlyRole(GUARDIAN) | GUARDIAN | DoS all operations |
| unpause() | onlyRole(ADMIN) | ADMIN | Restore operations |
| upgradeTo() | onlyRole(UPGRADER) | UPGRADER | Replace entire logic |
| setOracle() | onlyOwner | Owner | Control all price feeds |
| withdrawFees() | onlyRole(TREASURY) | TREASURY | Access accumulated fees |
| emergencyWithdraw() | onlyRole(ADMIN) | ADMIN | Drain all funds |
Step 2 — Analyze Role Hierarchy
Map the complete role structure:
DEFAULT_ADMIN_ROLE (can grant/revoke all roles)
├── ADMIN_ROLE
│ ├── Can upgrade contracts
│ ├── Can set critical parameters
│ └── Can call emergencyWithdraw
├── GUARDIAN_ROLE
│ ├── Can pause
│ └── Cannot unpause (prevents griefing)
├── FEE_MANAGER_ROLE
│ └── Can adjust fees within bounds
├── KEEPER_ROLE
│ └── Can trigger rebalancing
└── TREASURY_ROLE
└── Can withdraw protocol fees
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.
- 4d ago First seen · 232 lines · 19 tokens per session scan A d0b021ddf2b9
access-control-reviewer is an agent published in the GitHub repository ccashwell/evm-cortex (127 stars, last pushed 24d ago), licensed MIT. It adds 19 tokens to every session and 2,056 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.