Agent skill

Solidity Security

by ccashwell in ccashwell/evm-cortex

Security-focused Solidity development patterns. An agent skill from ccashwell/evm-cortex.

MITAuto-check passedBackend & APIs

Install Solidity Security

skills CLI
$ npx skills add ccashwell/evm-cortex --skill solidity-security -a claude-code

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

GitHub CLI
$ gh skill install ccashwell/evm-cortex solidity-security --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/solidity-security .claude/skills/solidity-security && 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
solidity-security
GitHub stars
131
Token cost
~1.5k tokens
SKILL.md length
190 words
Files
1
Skills in repo
89
Repo updated
First seen
Licence
MIT

At a glance

Security-focused Solidity development patterns. An agent skill from ccashwell/evm-cortex.

  • Writing contracts that handle funds
  • SKILL.md covers Reentrancy Guards, SafeERC20 — Always Use It, Access Control and Input Validation, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Interact with external tokens

What it does

Solidity Security is an agent skill from ccashwell/evm-cortex. Security-focused Solidity development patterns. Use when writing contracts that handle funds, interact with external tokens, or accept user input. Covers reentrancy guards, SafeERC20, access control, input validation, integer safety, and safe external calls.

Its SKILL.md is about 1.5k 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 contract auditing, Authorization and RBAC and 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

  • Writing contracts that handle funds
  • Interact with external tokens
  • Accept user input

Example prompts

  • “/solidity-security”

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

    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

Solidity Security loads about 1.5k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 190 words of instructions outside code blocks.

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

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). 190 words, ~1,473 tokens.

Download SKILL.mdSave it as .claude/skills/solidity-security/SKILL.md (or your agent's skills folder).
name
solidity-security
description
Security-focused Solidity development patterns. Use when writing contracts that handle funds, interact with external tokens, or accept user input. Covers reentrancy guards, SafeERC20, access control, input validation, integer safety, and safe external calls.

Solidity Security Fundamentals

Reentrancy Guards

Always use ReentrancyGuard on functions with external interactions, even when following CEI.

solidity
import {ReentrancyGuard} from "@openzeppelin/contracts/utils/ReentrancyGuard.sol";

contract Vault is ReentrancyGuard {
    mapping(address => uint256) public balances;

    function withdraw(uint256 amount) external nonReentrant {
        if (balances[msg.sender] < amount) revert InsufficientBalance();

        balances[msg.sender] -= amount;

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

SafeERC20 — Always Use It

Token contracts are not standardized in practice. USDT does not return a bool on transfer. USDC uses 6 decimals (not 18). Some tokens have fee-on-transfer. Always use SafeERC20.

solidity
import {IERC20} from "@openzeppelin/contracts/token/ERC20/IERC20.sol";
import {SafeERC20} from "@openzeppelin/contracts/token/ERC20/utils/SafeERC20.sol";

contract TokenVault {
    using SafeERC20 for IERC20;

    function deposit(IERC20 token, uint256 amount) external {
        // SafeERC20 handles non-standard return values
        token.safeTransferFrom(msg.sender, address(this), amount);
    }

    function withdraw(IERC20 token, uint256 amount) external {
        token.safeTransfer(msg.sender, amount);
    }

    function approveSpender(IERC20 token, address spender, uint256 amount) external {
        // forceApprove handles tokens requiring approval reset to 0 first (USDT)
        token.forceApprove(spender, amount);
    }
}
Token Decimal Gotchas
solidity
// WRONG: assuming 18 decimals
uint256 oneToken = 1e18;

// RIGHT: query decimals
uint8 decimals = IERC20Metadata(address(token)).decimals();
uint256 oneToken = 10 ** decimals;

// Common decimals:
// USDC: 6 decimals  (1 USDC = 1e6)
// USDT: 6 decimals  (1 USDT = 1e6)
// WBTC: 8 decimals  (1 WBTC = 1e8)
// DAI:  18 decimals (1 DAI  = 1e18)
// WETH: 18 decimals (1 WETH = 1e18)

Access Control

Use Ownable2Step over Ownable to prevent accidental ownership transfer to a wrong address.

solidity
import {Ownable2Step, Ownable} from "@openzeppelin/contracts/access/Ownable2Step.sol";

contract Protocol is Ownable2Step {
    constructor(address initialOwner) Ownable(initialOwner) {}

    function emergencyPause() external onlyOwner {
        _pause();
    }
}

For multi-role systems, use AccessControl:

solidity
bytes32 public constant PAUSER_ROLE = keccak256("PAUSER_ROLE");
bytes32 public constant MINTER_ROLE = keccak256("MINTER_ROLE");

function pause() external onlyRole(PAUSER_ROLE) {
    _pause();
}

Input Validation

Validate everything at system boundaries. Trust nothing from external callers.

solidity
error ZeroAddress();
error ZeroAmount();
error InvalidBps(uint256 bps);
error ArrayLengthMismatch();
error ExceedsMaximum(uint256 value, uint256 maximum);

function setFee(uint256 feeBps) external onlyOwner {
    if (feeBps > 10_000) revert InvalidBps(feeBps);
    fee = feeBps;
}

function batchTransfer(address[] calldata recipients, uint256[] calldata amounts) external {
    if (recipients.length != amounts.length) revert ArrayLengthMismatch();
    if (recipients.length == 0) revert ZeroAmount();

    for (uint256 i; i < recipients.length; ++i) {
        if (recipients[i] == address(0)) revert ZeroAddress();
        if (amounts[i] == 0) revert ZeroAmount();
        _transfer(recipients[i], amounts[i]);
    }
}

Safe External Calls

Never trust return data from arbitrary external calls.

solidity
function safeCall(address target, bytes calldata data)
    external
    returns (bytes memory)
{
    if (target.code.length == 0) revert NotAContract(target);

    (bool success, bytes memory returndata) = target.call(data);

    if (!success) {
        // Bubble up the revert reason
        if (returndata.length > 0) {
            assembly {
                revert(add(returndata, 0x20), mload(returndata))
            }
        }
        revert CallFailed(target);
    }

    return returndata;
}

ETH Transfer Safety

solidity
// BAD: transfer() has 2300 gas stipend, can break with EIP-1884
payable(recipient).transfer(amount);

// BAD: send() silently fails
payable(recipient).send(amount);

// GOOD: low-level call with success check
(bool success,) = recipient.call{value: amount}("");
if (!success) revert ETHTransferFailed();

Preventing Self-Destruct Force-Send

Contracts can receive ETH via selfdestruct even without receive(). Never rely on address(this).balance for accounting.

solidity
// BAD: relies on contract balance
function totalDeposits() external view returns (uint256) {
    return address(this).balance;
}

// GOOD: track deposits explicitly
uint256 public totalDeposited;

function deposit() external payable {
    totalDeposited += msg.value;
}

Security Checklist

  • All external calls follow checks-effects-interactions
  • ReentrancyGuard on functions with external interactions
  • SafeERC20 for all token operations
  • forceApprove instead of approve for USDT compatibility
  • No assumption of 18 decimals
  • Ownable2Step over Ownable
  • Zero-address checks on all address parameters
  • Array length validation for batch operations
  • call{} instead of transfer()/send() for ETH
  • Explicit accounting (don't rely on address(this).balance)
  • No tx.origin for auth
  • No hardcoded gas limits on external calls
  • Events emitted for all state changes

© 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/solidity-security of ccashwell/evm-cortex.

Open the folder on GitHubat commit f8f3301

Compare with similar skills

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

Solidity Security compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Solidity Security this skillccashwell/evm-cortex131—~1.5kAutomated safety check: PassMIT
Solidity Vulnerability Scanneralt-research2/SolidityGuard104—~1.6kAutomated safety check: NotesCustom licence
Smart Contract Auditelophanto/EloPhanto106—~2.7kAutomated safety check: PassCustom licence
Fizz Convertpashov/skills1.2k2 repos~3.7kAutomated safety check: PassMIT
Smart Contract Auditgreatpie/smart-contract-audit-skill101—~1.1kAutomated safety check: PassNone
Solidity AuditorGabson0x/bountyforge443—~3.7kAutomated safety check: PassNone

Similar skills

  • Solidity Vulnerability Scanner

    alt-research2/SolidityGuard

    Comprehensive Solidity contract security scanner detecting 104 vulnerability patterns across reentrancy, access control, arithmetic, DeFi, proxy, and token categories.

    104 GitHub stars~1.6k tokensUpdated 3 mo ago
    Backend & APIsAuto-check: notes
  • Smart Contract Audit

    elophanto/EloPhanto

    A skill your agent uses when reviewing a Solidity, Vyper, or Rust (Solana/Anchor) smart contract for paid audit work or pre-launch sanity check.

    106 GitHub stars~2.7k tokensUpdated 6 days ago
    SecurityAuto-check passed
  • 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
  • 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
  • Solidity Auditor

    Gabson0x/bountyforge

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

    443 GitHub stars~3.7k tokensUpdated 20 days ago
    Backend & APIsAuto-check passed
  • Solidity Auditor

    pashov/skills

    Security audit of Solidity code while you develop. An agent skill from pashov/skills.

    1.2k GitHub stars~9.9k tokensUpdated 2 days ago
    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 7 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 7 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 7 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 7 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 7 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 7 days ago
    Auto-check passed

Works with

Questions about Solidity Security

What does Solidity Security do?

Security-focused Solidity development patterns. An agent skill from ccashwell/evm-cortex. Solidity Security is an agent skill from ccashwell/evm-cortex. Security-focused Solidity development patterns.

When should I use Solidity Security?

Solidity Security fits situations like: writing contracts that handle funds; interact with external tokens; accept user input.

How do I install Solidity Security in Claude Code?

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

How do I install Solidity Security in Codex?

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

Can I use Solidity Security 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 solidity-security -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/solidity-security, .gemini/skills/solidity-security, .github/skills/solidity-security and .opencode/skills/solidity-security in your project.

What does Solidity Security need to run?

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

Does Solidity Security 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 Solidity Security 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 Solidity Security use?

Solidity Security 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 Solidity Security use?

About 1.5k tokens (SKILL.md is roughly 5.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 Solidity Security?

Skills that share tags, products or a category with Solidity Security: Solidity Vulnerability Scanner (alt-research2/SolidityGuard, 104 stars), Smart Contract Audit (elophanto/EloPhanto, 106 stars), Fizz Convert (pashov/skills, 1.2k stars) and Smart Contract Audit (greatpie/smart-contract-audit-skill, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Solidity Security?

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.