upgrade-planner

upgrade-planner is an agent for Claude Code from ccashwell/evm-cortex. It costs 20 tokens per session (1,477 once invoked), scanned A, original, MIT.

A planning agent for upgradeable smart contracts, which are blockchain programs whose code can be replaced while keeping their stored data and address. It focuses on proxy designs such as UUPS, Transparent, Beacon, and Diamond patterns.

In plain words
What is it for?
Use it to choose a proxy architecture, check storage layout safety, define upgrade permissions and paths, and plan deployment scripts for contract upgrades.
Why use it?
It helps avoid unsafe upgrades, especially lost or corrupted stored data and missing permission checks.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import {MyProtocolV2} from "../src/MyProtocolV2.sol";.

Good fit Use it to choose a proxy architecture, check storage layout safety, define upgrade permissions and paths, and plan deployment scripts for contract upgrades.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/ccashwell/evm-cortex
agentmods
npx agentmods add agents/ccashwell/evm-cortex/upgrade-planner

Made for: Claude Code.

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

agentmods badge for upgrade-planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/ccashwell/evm-cortex/upgrade-planner/github.svg)](https://agentmods.dev/agents/ccashwell/evm-cortex/upgrade-planner)
Your own site
<a href="https://agentmods.dev/agents/ccashwell/evm-cortex/upgrade-planner"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/upgrade-planner/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.

agentmods 80×15 button for upgrade-planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/ccashwell/evm-cortex/upgrade-planner"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/upgrade-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,477 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00020 $0.01477
Opus 5.5 $0.00008 $0.00591
Sonnet 5.5 $0.00004 $0.00295
Haiku 4.5 $0.00002 $0.00148

Measured 1mo ago against content hash 9b803203e70e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

agents/upgrade-planner.md · 152 lines

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 BeaconProxy instances; governance controls the UpgradeableBeacon

Read the full file on GitHub · 152 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. 1mo ago First seen · 152 lines · 20 tokens per session scan A 9b803203e70e

Subscribe to this mod's changes

upgrade-planner is an agent published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 20 tokens to every session and 1,477 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.

Related

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…

rjmurillo/ai-agents · 64 tokens

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.

criptogus/agent-evolve-network · 33 tokens

stellar-contracts

Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.

rylsherdamz-rgb/stellar-forge · 26 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

token-economics-designer

Token economics and tier design specialist. Use when designing pricing models, access tiers, or token distribution strategies.

Matt-Dionis/claude-code-configs · 28 tokens

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…

qdhenry/Claude-Command-Suite · 66 tokens