Fizz Convert
pashov/skills
Convert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes.
Upgrade vulnerability detection and prevention for Solidity proxy contracts.
$ npx skills add ccashwell/evm-cortex --skill upgrade-safety -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ccashwell/evm-cortex upgrade-safety --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ccashwell/evm-cortex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/upgrade-safety .claude/skills/upgrade-safety && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "upgrade-safety" agent skill from https://github.com/ccashwell/evm-cortex/tree/main/skills/upgrade-safety into .claude/skills/upgrade-safety/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-safety", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ccashwell/evm-cortex/tree/main/skills/upgrade-safetyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ccashwell/evm-cortex --skill upgrade-safety -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ccashwell/evm-cortex upgrade-safety --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccashwell/evm-cortex.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/upgrade-safety .agents/skills/upgrade-safety && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "upgrade-safety" agent skill from https://github.com/ccashwell/evm-cortex/tree/main/skills/upgrade-safety into .agents/skills/upgrade-safety/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-safety", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ccashwell/evm-cortex --skill upgrade-safety -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ccashwell/evm-cortex upgrade-safety --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccashwell/evm-cortex.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/upgrade-safety .cursor/skills/upgrade-safety && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "upgrade-safety" agent skill from https://github.com/ccashwell/evm-cortex/tree/main/skills/upgrade-safety into .cursor/skills/upgrade-safety/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-safety", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ccashwell/evm-cortex.git --path skills/upgrade-safety--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ccashwell/evm-cortex --skill upgrade-safety -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ccashwell/evm-cortex upgrade-safety --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccashwell/evm-cortex.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/upgrade-safety .gemini/skills/upgrade-safety && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "upgrade-safety" agent skill from https://github.com/ccashwell/evm-cortex/tree/main/skills/upgrade-safety into .gemini/skills/upgrade-safety/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-safety", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ccashwell/evm-cortex upgrade-safetyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ccashwell/evm-cortex --skill upgrade-safety -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ccashwell/evm-cortex.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/upgrade-safety .github/skills/upgrade-safety && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "upgrade-safety" agent skill from https://github.com/ccashwell/evm-cortex/tree/main/skills/upgrade-safety into .github/skills/upgrade-safety/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-safety", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ccashwell/evm-cortex --skill upgrade-safety -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ccashwell/evm-cortex upgrade-safety --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccashwell/evm-cortex.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/upgrade-safety .opencode/skills/upgrade-safety && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "upgrade-safety" agent skill from https://github.com/ccashwell/evm-cortex/tree/main/skills/upgrade-safety into .opencode/skills/upgrade-safety/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-safety", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
upgrade-safetyUpgrade vulnerability detection and prevention for Solidity proxy contracts.
Upgrade Safety is an agent skill from ccashwell/evm-cortex. Upgrade vulnerability detection and prevention for Solidity proxy contracts. Use when implementing UUPS, Transparent, or Diamond proxy patterns. Covers uninitialized proxy attacks, storage collisions, selector clashing, and upgrade safety validation tools.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Smart contracts. It works with Solidity and OpenZeppelin. The repository describes itself as: Ethereum protocol engineering squad for AI coding assistants. The licence is MIT.
Read from SKILL.md and the folder at commit f8f3301. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are solidity and bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Upgrade Safety loads about 1.7k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 216 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from ccashwell/evm-cortex at commit f8f3301, republished under its MIT licence (© ccashwell). 216 words, ~1,715 tokens.
.claude/skills/upgrade-safety/SKILL.md (or your agent's skills folder).The most common upgrade vulnerability. If initialize() isn't called on the proxy immediately after deployment, an attacker can front-run and take ownership.
// VULNERABLE: deployment and initialization are separate transactions
// Deploy proxy → attacker calls initialize() before admin
proxy = new ERC1967Proxy(implementation, "");
// ...gap where attacker calls initialize()...
VaultV1(proxy).initialize(admin);
// SAFE: initialize in the deployment transaction
bytes memory initData = abi.encodeCall(VaultV1.initialize, (admin));
proxy = new ERC1967Proxy(implementation, initData);contract VaultV1 is Initializable, OwnableUpgradeable {
/// @custom:oz-upgrades-unsafe-allow constructor
constructor() {
_disableInitializers();
}
function initialize(address admin) external initializer {
__Ownable_init(admin);
}
}Upgrading with a mismatched storage layout corrupts state.
// V1 Layout
contract VaultV1 {
address public owner; // slot 0
uint256 public totalSupply; // slot 1
uint256[48] private __gap;
}
// V2 BAD: inserted variable
contract VaultV2Bad {
address public owner; // slot 0
address public treasury; // slot 1 ← WAS totalSupply!
uint256 public totalSupply; // slot 2 ← shifted, reads __gap[0]
uint256[47] private __gap;
}
// V2 GOOD: appended variable
contract VaultV2Good {
address public owner; // slot 0
uint256 public totalSupply; // slot 1
address public treasury; // slot 2 ← new, was __gap[0]
uint256[47] private __gap; // reduced from 48 to 47
}# Compare storage layouts between versions
forge inspect src/VaultV1.sol:VaultV1 storage-layout --pretty > layout-v1.txt
forge inspect src/VaultV2.sol:VaultV2 storage-layout --pretty > layout-v2.txt
diff layout-v1.txt layout-v2.txtPre-Dencun, if the implementation contract contained selfdestruct and an attacker could trigger it, all proxies pointing to that implementation would be bricked.
// DANGEROUS: never include selfdestruct in implementations
contract BadImpl {
function destroy() external onlyOwner {
selfdestruct(payable(owner)); // bricks all proxies
}
}
// Post-Dencun (EIP-6780): selfdestruct only sends ETH unless in the
// same transaction as creation. Still, never use it in implementations.OpenZeppelin's initializer modifier includes reentrancy protection since v4.x. But custom initializers might not.
// VULNERABLE: custom initializer without reentrancy protection
bool private _initialized;
function initialize(address admin) external {
require(!_initialized);
// External call before setting _initialized
ICallback(admin).onInitialize(); // can re-enter initialize()
_initialized = true;
}
// SAFE: use OpenZeppelin's Initializable
function initialize(address admin) external initializer {
// modifier prevents reentrancy
}Base contracts without __gap cannot be extended in future versions without breaking derived contracts.
// BAD: no gap in base contract
abstract contract BaseV1 {
uint256 public value;
// no __gap — adding variables here shifts derived contract storage
}
contract DerivedV1 is BaseV1 {
uint256 public derivedValue; // slot 1
}
// GOOD: gap in base contract
abstract contract BaseV1 {
uint256 public value;
uint256[49] private __gap;
}
// Now BaseV2 can safely add variables:
abstract contract BaseV2 {
uint256 public value;
uint256 public newValue; // uses first __gap slot
uint256[48] private __gap;
}Proxy admin functions and implementation functions can have the same selector.
// TransparentUpgradeableProxy solves this by routing:
// - Admin calls → proxy logic (upgrade, admin functions)
// - Non-admin calls → delegated to implementation
// UUPS: implementation must include upgradeTo function
// Risk: implementation function selector collides with ERC-1967 functions
// Check selectors:
// upgradeTo(address) → 0x3659cfe6
// Ensure no implementation function has selector 0x3659cfe6# Detect selector collisions
forge inspect src/Vault.sol:Vault methodIdentifiers | sort
forge inspect src/Proxy.sol:Proxy methodIdentifiers | sort
# Compare for duplicatesUUPS proxies delegate upgrade authorization to the implementation. If a new implementation forgets _authorizeUpgrade, the proxy becomes un-upgradeable.
import {UUPSUpgradeable} from "@openzeppelin/contracts-upgradeable/proxy/utils/UUPSUpgradeable.sol";
contract VaultV1 is UUPSUpgradeable, OwnableUpgradeable {
function _authorizeUpgrade(address newImplementation)
internal
override
onlyOwner
{
// Can add additional validation here
// e.g., check newImplementation supports expected interface
}
}
// V2 MUST also include _authorizeUpgrade
// If omitted, proxy is permanently locked to V2
contract VaultV2 is UUPSUpgradeable, OwnableUpgradeable {
function _authorizeUpgrade(address newImplementation)
internal
override
onlyOwner
{}
}# Foundry: use forge-upgrades
forge install OpenZeppelin/openzeppelin-foundry-upgrades
# In tests: validate upgrade safety
import {Upgrades} from "openzeppelin-foundry-upgrades/Upgrades.sol";
function testUpgradeSafety() public {
Upgrades.validateUpgrade("VaultV2.sol:VaultV2", referenceContract);
}_disableInitializers() in implementation constructorforge inspect)__gap reduced by correct amountselfdestruct in implementation_authorizeUpgrade present in ALL versionsreinitializer(n) used for V2+ initialization (not initializer)© ccashwell, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/upgrade-safety of ccashwell/evm-cortex.
Open the folder on GitHubat commit f8f3301
Upgrade Safety next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Upgrade Safety this skillccashwell/evm-cortex | 131 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Fizz Convertpashov/skills | 1.2k | 2 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Feynman Auditor0xiehnnkta/nemesis-auditor | 243 | 1 repos | ~11k | Automated safety check: Pass | MIT | |
| Smart Contract Auditgreatpie/smart-contract-audit-skill | 101 | — | ~1.1k | Automated safety check: Pass | None | |
| RadarAuditware/radar | 154 | — | ~2.1k | Automated safety check: Pass | GPL-3.0 | |
| Solidity AuditorGabson0x/bountyforge | 442 | — | ~3.7k | Automated safety check: Pass | None |
pashov/skills
Convert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes.
0xiehnnkta/nemesis-auditor
Deep business logic bug finder using the Feynman technique. An agent skill from 0xiehnnkta/nemesis-auditor.
greatpie/smart-contract-audit-skill
Script-backed, out-of-box auditing workflow for Solidity/EVM repositories based on EVMbench detect/patch/exploit methodology.
Auditware/radar
Use radar for smart contract security analysis, AST generation, and detection template development.
Gabson0x/bountyforge
Security audit of Solidity code while you develop. An agent skill from Gabson0x/bountyforge.
Soneso/stellar-ios-mac-sdk
Guides Stellar blockchain development in Swift using stellar-ios-mac-sdk.
ccashwell/evm-cortex
A skill your agent uses when preparing for a security audit, performing reconnaissance on a new codebase, or creating a protocol overview.
ccashwell/evm-cortex
A skill your agent uses when integrating with Aave V3 for lending, borrowing, flash loans, or building on top of Aave markets.
ccashwell/evm-cortex
Access control design patterns for Solidity protocols. An agent skill from ccashwell/evm-cortex.
ccashwell/evm-cortex
A skill your agent uses when running a local Ethereum node with Anvil.
ccashwell/evm-cortex
A skill your agent uses when performing systematic breadth-first review of all contracts during a security audit.
ccashwell/evm-cortex
A skill your agent uses when performing deep analysis of specific findings or high-risk areas during a security audit.
Works with
Categories
Upgrade vulnerability detection and prevention for Solidity proxy contracts. Upgrade Safety is an agent skill from ccashwell/evm-cortex. Upgrade vulnerability detection and prevention for Solidity proxy contracts.
Upgrade Safety fits situations like: implementing UUPS; diamond proxy patterns.
Run `npx skills add ccashwell/evm-cortex --skill upgrade-safety -a claude-code`. Or copy the skill folder (skills/upgrade-safety in ccashwell/evm-cortex) into .claude/skills/upgrade-safety in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ccashwell/evm-cortex --skill upgrade-safety -a codex`. Or copy the skill folder (skills/upgrade-safety in ccashwell/evm-cortex) into .agents/skills/upgrade-safety in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ccashwell/evm-cortex --skill upgrade-safety -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/upgrade-safety, .gemini/skills/upgrade-safety, .github/skills/upgrade-safety and .opencode/skills/upgrade-safety in your project.
SKILL.md names no scripts, command-line tools or credentials: Upgrade Safety is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Upgrade Safety is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Upgrade Safety: Fizz Convert (pashov/skills, 1.2k stars), Feynman Auditor (0xiehnnkta/nemesis-auditor, 243 stars), Smart Contract Audit (greatpie/smart-contract-audit-skill, 101 stars) and Radar (Auditware/radar, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ccashwell (a GitHub user) maintains it in ccashwell/evm-cortex, which has 131 GitHub stars. The repository holds 89 skills in this directory. The repository was last updated on September 30, 2026.
Source: ccashwell/evm-cortex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.