Index of every page on this site: llms.txt
All skills
Run it yourself

Use when asked to audit or security-review EVM smart contracts: find vulnerabilities, judge exploit impact, or produce a ranked audit report. Not for guidance while the contracts are being written (`/security`).

Use this Skill: https://skilld.dev/gh/austintgriffith/ethskills/audit

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈55 tokens for metadata: the name and description. ≈917 when used: this file.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈219 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

EVM Smart Contract Audit

Audit unfamiliar contracts systematically, rank findings by real impact, and leave one concise report. Do not mutate the code or publish findings unless the user asks.

The Checklists

The checklist repository is pinned so two audits do not silently use different guidance:

CHECKLIST_REV=ffe4b670e78e1945bcf275f79d4b7b0481bcff35

Load a selected checklist from:

https://raw.githubusercontent.com/austintgriffith/evm-audit-skills/ffe4b670e78e1945bcf275f79d4b7b0481bcff35/<skill-name>/references/checklist.md

For a narrow question, load only the one or two relevant checklists. For a full codebase audit, always load evm-audit-general and evm-audit-precision-math, then add only the domains the code actually uses (normally 5–8 total). This keeps the review focused and avoids spending context on unrelated vulnerability classes.

Skills Available

Skill When to Load
evm-audit-general Always
evm-audit-precision-math Always
evm-audit-erc20 Contract interacts with ERC20 tokens
evm-audit-defi-amm AMM, DEX, Uniswap V3/V4, liquidity pools
evm-audit-defi-lending Lending, borrowing, CDP, liquidations
evm-audit-defi-staking Staking, liquid staking, restaking, EigenLayer
evm-audit-erc4626 Vaults, share/asset conversion
evm-audit-erc4337 Account abstraction, paymasters, session keys
evm-audit-bridges Cross-chain, LayerZero, CCIP, Wormhole
evm-audit-proxies Upgradeable contracts, UUPS, Transparent, Diamond
evm-audit-signatures Off-chain signatures, EIP-712, permits
evm-audit-governance DAO voting, timelocks, multi-sig
evm-audit-oracles Chainlink, TWAP, Pyth, price feeds
evm-audit-assembly Inline assembly, Yul, CREATE2
evm-audit-chain-specific Non-mainnet: Arbitrum, OP, zkSync, Blast, BSC
evm-audit-flashloans Flash loan attack vectors
evm-audit-erc721 NFTs, ERC721, ERC1155
evm-audit-dos DoS, unbounded loops, gas griefing
evm-audit-access-control Ownership, roles, centralization risks

How To Run An Audit

  1. Read the README, deployment assumptions, tests, and every in-scope contract before routing.
  2. Map assets, trust boundaries, privileged paths, external calls, accounting invariants, signatures, oracle dependencies, and chain-specific assumptions.
  3. Select checklists from the table above. Use one or two for a narrow question and normally 5–8 for a full audit.
  4. For a full audit, run one specialist per selected domain in parallel when sub-agents are available. Do not require a particular model.
  5. Give every specialist the same scope and ask it to return complete findings to the orchestrator: severity, location, preconditions, exploit/failure path, impact, and remediation. Treat files such as findings-<skill>.md as optional scratch space, not as the transport between agents.
  6. Deduplicate and verify findings against the code. Separate currently exploitable issues from risks that depend on future assets, configuration, or integrations.
  7. Write the requested report, ranking by demonstrated impact and exploitability. Clean up scratch files when the user requested a single deliverable.
  8. Never file GitHub issues or otherwise publish findings unless the user explicitly asks, identifies the target repository, and confirms the outbound action.

Sources

Built from research by Dacian, beirao.xyz, Sigma Prime, RareSkills, Decurity, weird-erc20, Spearbit, Hacken, OpenZeppelin, Cyfrin, and more. Full attribution: https://github.com/austintgriffith/evm-audit-skills#attribution--thanks

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warnings28d4 checks · Risk SAFE
  • Gen Agent Trust Hub28d

    The skill provides a framework for auditing EVM smart contracts by fetching checklists and methodologies from the author's GitHub repository. It defines a systematic process for sub-agents to analyze contract code and report findings. No malicious behavior, obfuscation, or unauthorized data access was identified.

  • Socket28d

    1 alert: gptSecurity

  • Snyk28d

    Risk: MEDIUM · 2 issues

  • Runlayer8mo

    1 file scanned · No issues

Signed by skilld at 47779e7. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 weeks ago.

Activeupdated last month

README badge

README badge for austintgriffith/ethskills/audit