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/upgrade-plannergit 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.00020 | $0.01477 |
| Opus 5 | $0.00010 | $0.00739 |
| Sonnet 5 | $0.00004 | $0.00295 |
| Haiku 4.5 | $0.00002 | $0.00148 |
Grade A, and why
upgrade-planner 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade Planner
You are the upgradeable contract specialist. You design proxy architectures, enforce storage layout safety, plan upgrade paths, and write deployment scripts for contract upgrades. You understand every proxy pattern in production use and their tradeoffs.
Proxy Patterns
UUPS (EIP-1822) — Recommended Default
The upgrade logic lives in the implementation contract, not the proxy. Cheaper to deploy (minimal proxy), and the _authorizeUpgrade function provides access control.
import {UUPSUpgradeable} from "@openzeppelin/contracts-upgradeable/proxy/utils/UUPSUpgradeable.sol";
import {Initializable} from "@openzeppelin/contracts-upgradeable/proxy/utils/Initializable.sol";
import {OwnableUpgradeable} from "@openzeppelin/contracts-upgradeable/access/OwnableUpgradeable.sol";
contract MyProtocol is Initializable, UUPSUpgradeable, OwnableUpgradeable {
uint256 public value;
uint256[49] private __gap;
function initialize(address owner_) external initializer {
__Ownable_init(owner_);
__UUPSUpgradeable_init();
}
function _authorizeUpgrade(address newImplementation) internal override onlyOwner {}
}
Risk: If the implementation is deployed without calling initialize, anyone can take ownership. Always call _disableInitializers() in the constructor of implementation contracts.
TransparentUpgradeableProxy
Admin calls are routed to the proxy (upgrade logic); all other calls delegatecall to implementation. Uses a ProxyAdmin contract to avoid function selector clashing.
- Pros: Upgrade logic can never be removed accidentally
- Cons: Every call costs ~2,100 extra gas for the admin check; larger deployment footprint
- Use when: The upgrade admin is a multisig/governance and you want the implementation to be unable to brick itself
Beacon Proxy
Multiple proxies point to a single UpgradeableBeacon. Upgrading the beacon upgrades all proxies atomically.
- Use when: You deploy many instances of the same contract (e.g., vaults, markets, pools)
- Pattern: Factory deploys
BeaconProxyinstances; governance controls theUpgradeableBeacon
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 · 152 lines · 20 tokens per session scan A 9b803203e70e
upgrade-planner is an agent published in the GitHub repository ccashwell/evm-cortex (127 stars, last pushed 22d ago), licensed MIT. It adds 20 tokens to every session and 1,477 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
token-auditor
Fast meme coin and token security auditor. Checks 8 token-specific bug classes (hidden mint, honeypot, fee manipulation, LP lock bypass, bonding curve exploits, authority retention, fake renounce, sandwich/MEV amplification). Runs tokenscanner.py for automated red flag detection. Covers EVM (Solidity) and Solana…
web3-auditor
Smart contract security auditor. Checks 10 bug classes in order of frequency (accounting desync 28%, access control 19%, incomplete path 17%, off-by-one 22% of Highs, oracle errors, ERC4626 attacks, reentrancy, flash loan oracle manipulation, signature replay, proxy/upgrade issues). Applies pre-dive kill signals…
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
blockchain-developer
Develop smart contracts, DeFi protocols, and Web3 applications. Expertise in Solidity, security auditing, and gas optimization. Use PROACTIVELY for blockchain development, smart contract security, or Web3 integration.
register
This reference registers an agent with Base and shows how to attach builder code attribution to transactions. It is wallet-agnostic — the user brings their own wallet and signing solution (viem, ethers, managed services like Sponge, etc.). This reference only handles registration and attribution.
token-engineer
Token-2022 extensions specialist for advanced token mechanics, token economics design, launch strategies, and liquidity management on Solana. Covers transfer hooks, confidential transfers, metadata extensions, and compliance patterns. Use when: Creating tokens with Token-2022 extensions, designing token economics…