solidity-patterns

solidity-patterns is a skill for Claude Code, Codex from ccashwell/evm-cortex. It costs 58 tokens per session (1,363 once invoked), scanned A, original, MIT.

A guide to design patterns for Solidity smart contracts, including how to order state changes and external calls, restrict access, model states, and distribute funds safely.

In plain words
What is it for?
Use it when writing, reviewing, or refactoring contracts with withdrawals, rewards, permissions, state transitions, or commit-reveal flows.
Why use it?
It helps developers structure contract logic consistently and avoid common bugs such as reentrancy and blocked payments.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when writing, reviewing, or refactoring contracts with withdrawals, rewards, permissions, state transitions, or commit-reveal flows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ccashwell/evm-cortex/solidity-patterns
Install

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.

Any agent
npx skills add ccashwell/evm-cortex --skill solidity-patterns
Clone the repo
git clone --depth 1 https://github.com/ccashwell/evm-cortex

Made for: Claude Code, Codex.

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 solidity-patterns

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/ccashwell/evm-cortex/solidity-patterns"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/solidity-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,363 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00058 $0.01363
Opus 5.5 $0.00023 $0.00545
Sonnet 5.5 $0.00012 $0.00273
Haiku 4.5 $0.00006 $0.00136

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

Security

Grade A, and why

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

skills/solidity-patterns/SKILL.md · 218 lines

How it starts

The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Solidity Design Patterns

Checks-Effects-Interactions (CEI)

The most critical pattern in Solidity. All functions that interact with external contracts must follow this order:

  1. Checks — validate inputs and preconditions
  2. Effects — update state
  3. Interactions — call external contracts
function withdraw(uint256 amount) external {
    // CHECKS
    if (amount == 0) revert ZeroAmount();
    if (balances[msg.sender] < amount) revert InsufficientBalance();

    // EFFECTS
    balances[msg.sender] -= amount;

    // INTERACTIONS
    (bool success,) = msg.sender.call{value: amount}("");
    if (!success) revert TransferFailed();

    emit Withdrawn(msg.sender, amount);
}

Violating CEI is the root cause of reentrancy. Even with ReentrancyGuard, always write CEI-compliant code as defense in depth.

Pull-Over-Push

Never iterate over recipients to push funds. Let users withdraw (pull) their own funds.

// BAD: Push pattern — one revert blocks everyone
function distributeRewards(address[] calldata recipients, uint256[] calldata amounts) external {
    for (uint256 i; i < recipients.length; ++i) {
        payable(recipients[i]).transfer(amounts[i]); // reverts if any fails
    }
}

// GOOD: Pull pattern — each user claims independently
mapping(address => uint256) public pendingRewards;

function claimReward() external {
    uint256 amount = pendingRewards[msg.sender];
    if (amount == 0) revert NothingToClaim();

    pendingRewards[msg.sender] = 0;

    (bool success,) = msg.sender.call{value: amount}("");
    if (!success) revert TransferFailed();

    emit RewardClaimed(msg.sender, amount);
}

Guard Check Pattern

Centralize validation in modifiers or internal functions for reuse and consistency.

error Unauthorized();
error InvalidAmount();
error Expired(uint256 deadline);

modifier onlyWhitelisted() {
    if (!whitelist[msg.sender]) revert Unauthorized();
    _;
}

modifier validAmount(uint256 amount) {
    if (amount == 0 || amount > MAX_AMOUNT) revert InvalidAmount();
    _;
}

modifier beforeDeadline(uint256 deadline) {
    if (block.timestamp > deadline) revert Expired(deadline);
    _;
}

function deposit(uint256 amount, uint256 deadline)
    external
    onlyWhitelisted
    validAmount(amount)
    beforeDeadline(deadline)
{
    // core logic only — all checks in modifiers
}

Read the full file on GitHub · 218 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 · 218 lines · 58 tokens per session scan A 56e32a6ac501

Subscribe to this mod's changes

solidity-patterns is a skill published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 58 tokens to every session and 1,363 once invoked, about $0.0002 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-09-03.