web3-audit

Audit Solidity smart contracts using DeFi bug-class playbooks and Foundry PoC templates.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/jellaharshith/SWIFT --skill web3-audit-jellaharshith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web3-audit
Source: https://github.com/jellaharshith/SWIFT/tree/main/swift/skills/cbh/skills/web3-audit
Command: npx skills add https://github.com/jellaharshith/SWIFT --skill web3-audit-jellaharshith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly evaluate and audit Solidity/Rust smart contracts by mapping common high-impact DeFi bug classes to concrete pre-dive checks, grep-based code review prompts, and reusable Foundry PoC scaffolding.

Core Features & Use Cases

  • 10 DeFi bug classes: accounting state desync, access control, incomplete code paths, off-by-one/boundaries, oracle manipulation, ERC4626 vault attacks, reentrancy, flash loan attacks, signature replay, and proxy/upgrade issues.
  • Pre-dive kill signals & target scoring: decide whether a dive is worth it using TVL thresholds, audit history indicators, code complexity heuristics, and engagement scoring rules.
  • Practical testing workflow outputs: provides grep patterns to locate relevant code regions plus a Foundry PoC template structure for turning hypotheses into executable tests.
  • Use for: auditing DeFi protocols you plan to hunt, validating whether a contract’s architecture makes certain exploit classes more/less likely, and preparing a structured audit checklist before deep manual review.

Quick Start

Use the web3-audit skill to audit a Solidity/DeFi target by following its pre-dive kill signals, then running the provided grep patterns to identify where each bug class could apply.

Frequently Asked Questions about web3-audit

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

FAQPage Schema
How do I audit a DeFi smart contract for common vulnerability classes?

To audit a DeFi smart contract, use a structured playbook that maps 10 high-impact bug classes like oracle manipulation, reentrancy, and access control to pre-dive checks, grep patterns, and Foundry PoC templates for executable testing.

What are pre-dive kill signals in a smart contract security audit?

Pre-dive kill signals in a smart contract security audit are scoring rules using TVL thresholds, audit history, and code complexity heuristics to determine if a DeFi target is worth reviewing before committing to a deep manual dive.

How do I find flash loan and reentrancy vulnerabilities in Solidity code?

You can find flash loan and reentrancy vulnerabilities by applying targeted grep patterns to locate relevant code regions, then validating the identified logic flaws using a reusable Foundry PoC template scaffold.

Does this DeFi audit workflow cover ERC4626 vault attacks and upgradeable proxies?

Yes, this DeFi audit workflow covers ERC4626 vault attacks and upgradeable proxy issues, evaluating accounting state desync, signature replay, and boundary conditions across Solidity and related contract bases.

What is the best way to prepare a security checklist for Solidity smart contracts?

The best way to prepare a security checklist for Solidity smart contracts is to use a deterministic framework that scores target engagement and maps grep-based search requirements across 10 defined DeFi bug classes before deep manual review.

When should I not use a grep-based approach for smart contract security audits?

You should not use a grep-based approach for smart contract security audits when the DeFi target fails pre-dive kill signals, such as low TVL thresholds or clean audit history, indicating a deep manual dive is not worth the effort.