Agent skill

Delegate Call Risks

by ccashwell in ccashwell/evm-cortex

Delegatecall risks and safety patterns for Solidity proxies and modular contracts.

MITAuto-check passedBackend & APIs

Install Delegate Call Risks

skills CLI
$ npx skills add ccashwell/evm-cortex --skill delegate-call-risks -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ccashwell/evm-cortex delegate-call-risks --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ccashwell/evm-cortex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/delegate-call-risks .claude/skills/delegate-call-risks && rm -rf skills-src

Use ~/.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/

Facts

Skill name
delegate-call-risks
GitHub stars
131
Token cost
~1.7k tokens
SKILL.md length
276 words
Files
1
Skills in repo
89
Repo updated
First seen
Licence
MIT

At a glance

Delegatecall risks and safety patterns for Solidity proxies and modular contracts.

  • Implementing upgradeable proxies
  • SKILL.md covers How Delegatecall Works, Storage Layout Must Match, Context Preservation and Proxy Initialization Attack, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Diamond patterns

What it does

Delegate Call Risks is an agent skill from ccashwell/evm-cortex. Delegatecall risks and safety patterns for Solidity proxies and modular contracts. Use when implementing upgradeable proxies, diamond patterns, or any contract using delegatecall. Covers storage layout requirements, context preservation, and implementation safety.

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. The repository describes itself as: Ethereum protocol engineering squad for AI coding assistants. The licence is MIT.

When your agent uses it

  • Implementing upgradeable proxies
  • Diamond patterns
  • Any contract using delegatecall

Example prompts

  • “/delegate-call-risks”

What it can do on your machine

Read from SKILL.md and the folder at commit f8f3301. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Delegate Call Risks loads about 1.7k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 276 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from ccashwell/evm-cortex at commit f8f3301, republished under its MIT licence (© ccashwell). 276 words, ~1,715 tokens.

Download SKILL.mdSave it as .claude/skills/delegate-call-risks/SKILL.md (or your agent's skills folder).
name
delegate-call-risks
description
Delegatecall risks and safety patterns for Solidity proxies and modular contracts. Use when implementing upgradeable proxies, diamond patterns, or any contract using delegatecall. Covers storage layout requirements, context preservation, and implementation safety.

Delegatecall Risks

How Delegatecall Works

delegatecall executes the target's code in the caller's context: the caller's storage, msg.sender, msg.value, and address(this) are preserved.

Proxy (storage)  →  delegatecall  →  Implementation (code)
- slot 0: admin      executes in       reads/writes Proxy's storage
- slot 1: value      Proxy context      msg.sender = original caller

Storage Layout Must Match

The proxy and implementation must have identical storage layouts. Delegatecall operates on slot numbers, not variable names.

solidity
// PROXY storage layout:
// slot 0: address admin
// slot 1: uint256 totalDeposits

// Implementation V1 — MUST match proxy layout
contract VaultV1 {
    address public admin;        // slot 0 ✓
    uint256 public totalDeposits; // slot 1 ✓
}

// Implementation V2 — DANGEROUS: inserted variable shifts layout
contract VaultV2Bad {
    address public admin;           // slot 0 ✓
    address public feeRecipient;    // slot 1 ✗ (was totalDeposits!)
    uint256 public totalDeposits;   // slot 2 ✗ (shifted!)
}

// Implementation V2 — SAFE: appended variable
contract VaultV2Good {
    address public admin;           // slot 0 ✓
    uint256 public totalDeposits;   // slot 1 ✓
    address public feeRecipient;    // slot 2 (new, appended)
}

Context Preservation

Inside a delegatecall, all context variables refer to the proxy:

solidity
contract Implementation {
    function whoAmI() external view returns (address self, address sender, uint256 val) {
        self = address(this);    // proxy address (NOT implementation)
        sender = msg.sender;     // original caller (NOT proxy)
        val = msg.value;         // original value sent to proxy
    }
}

Proxy Initialization Attack

If the implementation contract's initialize() isn't disabled, an attacker can call it directly.

solidity
// VULNERABLE: implementation can be initialized
contract VaultImpl is Initializable {
    function initialize(address admin) external initializer {
        _admin = admin;
    }
}
// Attacker calls VaultImpl.initialize(attackerAddress) directly

// SAFE: disable initializers in constructor
contract VaultImpl is Initializable {
    /// @custom:oz-upgrades-unsafe-allow constructor
    constructor() {
        _disableInitializers();
    }

    function initialize(address admin) external initializer {
        _admin = admin;
    }
}

Implementation Slot Poisoning

Pre-Dencun, an attacker could initialize the implementation and then selfdestruct it, bricking all proxies pointing to it.

solidity
// Pre-Dencun attack (selfdestruct still worked):
// 1. Call initialize() on implementation → become owner
// 2. Call selfdestruct → implementation code deleted
// 3. All proxies delegatecall to empty address → all calls succeed with no-op
// 4. Protocol is bricked

// Defense: _disableInitializers() + no selfdestruct in implementation
// Post-Dencun: selfdestruct only sends ETH, doesn't delete code (EIP-6780)

Delegatecall to Untrusted Contracts

Never delegatecall to an address controlled by users or external parties.

solidity
// VULNERABLE: user controls the target
function execute(address target, bytes calldata data) external {
    (bool success,) = target.delegatecall(data); // target can write to any storage slot
    require(success);
}

// SAFE: restrict to known, audited implementations
mapping(address => bool) public approvedImplementations;

function execute(address target, bytes calldata data) external onlyOwner {
    if (!approvedImplementations[target]) revert UnapprovedTarget();
    (bool success,) = target.delegatecall(data);
    if (!success) revert ExecutionFailed();
}

Function Selector Clashing

In UUPS/Transparent proxies, if the proxy and implementation have functions with the same selector, one will shadow the other.

solidity
// Transparent Proxy pattern avoids this:
// - Admin calls → handled by proxy (upgrade functions)
// - Non-admin calls → delegated to implementation

// UUPS pattern: implementation handles upgrades
// Risk: custom function selector collides with upgradeTo(address)
// Always check: forge inspect Contract methodIdentifiers
Checking for Selector Collisions
bash
# List all function selectors
forge inspect src/Vault.sol:Vault methodIdentifiers

# Compare proxy and implementation selectors for collisions
# Any match = potential shadowing issue

Storage Gap Pattern

Reserve storage slots in base contracts for future upgrades.

solidity
abstract contract BaseVaultV1 {
    uint256 public totalDeposits;
    mapping(address => uint256) public balances;

    uint256[48] private __gap; // reserve 48 slots
}

// V2: add new variable, reduce gap
abstract contract BaseVaultV2 {
    uint256 public totalDeposits;
    mapping(address => uint256) public balances;
    uint256 public withdrawalDelay; // new in V2

    uint256[47] private __gap; // 48 - 1 = 47
}

EIP-1967 Standard Slots

Proxy metadata stored at pseudo-random slots to avoid collisions with implementation storage.

solidity
// Implementation address slot
bytes32 constant IMPLEMENTATION_SLOT =
    0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc;

// Admin address slot
bytes32 constant ADMIN_SLOT =
    0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103;

function _getImplementation() internal view returns (address impl) {
    assembly {
        impl := sload(IMPLEMENTATION_SLOT)
    }
}

UUPS vs Transparent Proxy

FeatureUUPSTransparent
Upgrade logicIn implementationIn proxy
Gas cost per callLower (no admin check)Higher (admin check every call)
Deploy costLower proxyHigher proxy
RiskForget upgradeTo in new impl → brickedMore gas per user call
Admin collisionPossiblePrevented by admin routing

Delegatecall Safety Checklist

  • Storage layout verified with forge inspect --storage-layout before upgrade
  • New variables only appended, never inserted
  • __gap reduced by correct amount for new variables
  • _disableInitializers() in implementation constructor
  • No selfdestruct in implementation code
  • No delegatecall to user-controlled addresses
  • Function selector collisions checked between proxy and implementation
  • Inheritance order unchanged between versions
  • OpenZeppelin Upgrades plugin used for validation
  • Upgrade tested on fork before mainnet

© ccashwell, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/delegate-call-risks of ccashwell/evm-cortex.

Open the folder on GitHubat commit f8f3301

Compare with similar skills

Delegate Call Risks 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.

Delegate Call Risks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Delegate Call Risks this skillccashwell/evm-cortex131—~1.7kAutomated safety check: PassMIT
Fizz Convertpashov/skills1.2k2 repos~3.7kAutomated safety check: PassMIT
Feynman Auditor0xiehnnkta/nemesis-auditor2441 repos~11kAutomated safety check: PassMIT
Smart Contract Auditgreatpie/smart-contract-audit-skill101—~1.1kAutomated safety check: PassNone
RadarAuditware/radar154—~2.1kAutomated safety check: PassGPL-3.0
Solidity AuditorGabson0x/bountyforge443—~3.7kAutomated safety check: PassNone

Similar skills

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

    1.2k GitHub starsUsed in 2 repos~3.7k tokens
    Backend & APIsAuto-check passed
  • Feynman Auditor

    0xiehnnkta/nemesis-auditor

    Deep business logic bug finder using the Feynman technique. An agent skill from 0xiehnnkta/nemesis-auditor.

    244 GitHub starsUsed in 1 repo~11k tokens
    Backend & APIsAuto-check passed
  • Smart Contract Audit

    greatpie/smart-contract-audit-skill

    Script-backed, out-of-box auditing workflow for Solidity/EVM repositories based on EVMbench detect/patch/exploit methodology.

    101 GitHub stars~1.1k tokensUpdated 7 mo ago
    Backend & APIsAuto-check passed
  • Radar

    Auditware/radar

    Use radar for smart contract security analysis, AST generation, and detection template development.

    154 GitHub stars~2.1k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Solidity Auditor

    Gabson0x/bountyforge

    Security audit of Solidity code while you develop. An agent skill from Gabson0x/bountyforge.

    443 GitHub stars~3.7k tokensUpdated 21 days ago
    Backend & APIsAuto-check passed
  • Add Explorer

    lidofinance/diffyscan

    Adds or repairs Diffyscan explorer API routing and response adapters for a new host, chain or payload format.

    142 GitHub stars~1k tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from ccashwell/evm-cortex

All 89 skills in this repo
  • Xray Pre Audit

    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.

    131 GitHub stars~25k tokensUpdated 8 days ago
    Auto-check passed
  • Aave Integration

    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.

    131 GitHub stars~1.3k tokensUpdated 8 days ago
    Auto-check passed
  • Access Control Patterns

    ccashwell/evm-cortex

    Access control design patterns for Solidity protocols. An agent skill from ccashwell/evm-cortex.

    131 GitHub stars~1.8k tokensUpdated 8 days ago
    Auto-check passed
  • Anvil Patterns

    ccashwell/evm-cortex

    A skill your agent uses when running a local Ethereum node with Anvil.

    131 GitHub stars~1.3k tokensUpdated 8 days ago
    Auto-check passed
  • Audit Breadth Scan

    ccashwell/evm-cortex

    A skill your agent uses when performing systematic breadth-first review of all contracts during a security audit.

    131 GitHub stars~1.4k tokensUpdated 8 days ago
    Auto-check passed
  • Audit Depth Analysis

    ccashwell/evm-cortex

    A skill your agent uses when performing deep analysis of specific findings or high-risk areas during a security audit.

    131 GitHub stars~1.6k tokensUpdated 8 days ago
    Auto-check passed

Works with

Categories

Questions about Delegate Call Risks

What does Delegate Call Risks do?

Delegatecall risks and safety patterns for Solidity proxies and modular contracts. Delegate Call Risks is an agent skill from ccashwell/evm-cortex. Delegatecall risks and safety patterns for Solidity proxies and modular contracts.

When should I use Delegate Call Risks?

Delegate Call Risks fits situations like: implementing upgradeable proxies; diamond patterns; any contract using delegatecall.

How do I install Delegate Call Risks in Claude Code?

Run `npx skills add ccashwell/evm-cortex --skill delegate-call-risks -a claude-code`. Or copy the skill folder (skills/delegate-call-risks in ccashwell/evm-cortex) into .claude/skills/delegate-call-risks in your project. Claude Code loads it when a task matches its description.

How do I install Delegate Call Risks in Codex?

Run `npx skills add ccashwell/evm-cortex --skill delegate-call-risks -a codex`. Or copy the skill folder (skills/delegate-call-risks in ccashwell/evm-cortex) into .agents/skills/delegate-call-risks in your project. Codex loads it when a task matches its description.

Can I use Delegate Call Risks in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ccashwell/evm-cortex --skill delegate-call-risks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/delegate-call-risks, .gemini/skills/delegate-call-risks, .github/skills/delegate-call-risks and .opencode/skills/delegate-call-risks in your project.

What does Delegate Call Risks need to run?

SKILL.md names no scripts, command-line tools or credentials: Delegate Call Risks is instructions for the agent only.

Does Delegate Call Risks access the network?

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.

Is Delegate Call Risks safe to install?

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.

What licence does Delegate Call Risks use?

Delegate Call Risks is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Delegate Call Risks use?

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.

What are the alternatives to Delegate Call Risks?

Skills that share tags, products or a category with Delegate Call Risks: Fizz Convert (pashov/skills, 1.2k stars), Feynman Auditor (0xiehnnkta/nemesis-auditor, 244 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.

Who maintains Delegate Call Risks?

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.