proxy-upgrade-safety

Detect vulnerabilities in upgradeable proxy smart contracts across multiple proxy patterns.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/dajneem23/codex-skills --skill proxy-upgrade-safety-dajneem23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proxy-upgrade-safety
Source: https://github.com/dajneem23/codex-skills/tree/main/proxy-upgrade-safety
Command: npx skills add https://github.com/dajneem23/codex-skills --skill proxy-upgrade-safety-dajneem23

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies critical vulnerabilities in upgradeable smart contract proxy patterns, preventing potential exploits that could lead to storage corruption, unauthorized upgrades, or complete contract takeover.

Core Features & Use Cases

  • Storage Collision Detection: Analyzes storage layouts between proxy and implementation versions to prevent data corruption.
  • Initialization Safety: Verifies that implementation contracts are securely initialized to prevent front-running attacks.
  • Upgrade Authorization Checks: Ensures that upgrade functions have proper access controls to prevent unauthorized changes.
  • Use Case: When auditing a DeFi protocol that uses UUPS proxies, this Skill will automatically check for common pitfalls like uninitialized implementations or missing access control on the _authorizeUpgrade function.

Quick Start

Analyze the provided proxy contract code for storage layout collisions and initialization vulnerabilities.

Frequently Asked Questions about proxy-upgrade-safety

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit upgradeable proxy smart contracts for storage layout collisions?

Auditing upgradeable proxy smart contracts for storage layout collisions involves analyzing storage layouts between proxy and implementation versions to detect overlapping variables and prevent data corruption.

What security vulnerabilities affect UUPS and Transparent Proxy patterns?

Security vulnerabilities affecting UUPS and Transparent Proxy patterns include uninitialized implementations, function selector clashing, delegatecall context issues, and missing access controls on upgrade authorization functions.

How do I verify initialization safety and prevent front-running attacks in Solidity proxies?

To verify initialization safety and prevent front-running attacks in Solidity proxies, check that implementation contracts are securely initialized with proper access controls preventing unauthorized contract takeover.

Does this proxy audit analysis support Diamond (EIP-2535) and Beacon patterns?

This proxy audit analysis supports Diamond (EIP-2535), Beacon, Transparent Proxy, UUPS (EIP-1822), and Minimal Proxy (EIP-1167) patterns for verifying delegatecall architectures and upgrade path safety.

What is the best way to check delegatecall context issues in upgradeable contracts?

The best way to check delegatecall context issues in upgradeable contracts is to analyze the delegatecall architecture for storage pointer corruption and verify compliance with established proxy patterns.