foundry-poc-mainnet-fork

Generate Foundry proof-of-concept tests reproducing exploits on forked EVM networks.

71|18|Updated Apr 23, 2026

Search Tags:#security audit #smart contracts #foundry #evm #mainnet fork #vulnerability reproduction #poc generation

Ready to run

npx skills add https://github.com/cholakovvv/foundry-poc-mainnet-fork --skill foundry-poc-mainnet-fork

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: foundry-poc-mainnet-fork
Source: https://github.com/cholakovvv/foundry-poc-mainnet-fork/tree/main
Command: npx skills add https://github.com/cholakovvv/foundry-poc-mainnet-fork --skill foundry-poc-mainnet-fork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the time-consuming work of turning smart contract vulnerability reports into reproducible Foundry proof-of-concept tests by guiding the creation of end-to-end mainnet fork reproductions.

Core Features & Use Cases

Mainnet Fork PoC Generation: Creates Foundry tests that interact with real deployed EVM contracts and reproduce vulnerabilities from trigger action to final impact.
Security Finding Classification: Classifies findings as frozen historical, forward-looking, or both before building the reproduction path.
Use Case: Smart contract security researchers can provide a vulnerability report, chain details, fork target, and deployed addresses to generate a submission-ready PoC without mocks or artificial protocol state changes.

Quick Start

Use the foundry-poc-mainnet-fork skill to reproduce this smart contract vulnerability on a Foundry mainnet fork using the provided deployed contract addresses.

Frequently Asked Questions about foundry-poc-mainnet-fork

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

FAQPage Schema

How do I generate a Foundry proof-of-concept test for a smart contract vulnerability on a mainnet fork?▼

To generate a Foundry PoC, provide a vulnerability report, chain details, fork target, and deployed contract addresses to reproduce the exploit end-to-end against real EVM contracts on a mainnet fork. This creates a submission-ready test without mocks.

What is the best way to reproduce a smart contract exploit using real protocol state?▼

Reproducing a smart contract exploit using real protocol state involves creating Foundry tests that interact with real deployed EVM contracts on a forked network, executing the vulnerability from trigger action to final impact to assert causal-chain execution.

Do I need verified contract addresses to run a mainnet fork PoC in Foundry?▼

Yes, verified contract addresses are required to run a mainnet fork PoC in Foundry. You also need chain details and fork configuration to accurately reproduce vulnerability interactions against real deployed contracts without artificial protocol state changes.

Can I classify security findings as frozen historical or forward-looking before building a reproduction path?▼

Yes, security findings are classified as frozen historical, forward-looking, or both before building the reproduction path. This classification step ensures the mainnet fork PoC accurately targets the correct temporal context of the vulnerability.

Does this approach work for bug bounty submissions requiring mainnet state assertions?▼

Yes, this approach works for bug bounty submissions requiring mainnet state assertions. It generates end-to-end Foundry proof-of-concept tests that validate vulnerabilities and assert impact using real protocol interactions on forked EVM networks.

Why should I not use mocks when reproducing EVM vulnerabilities for security audits?▼

Mocks are not used because they introduce artificial protocol state changes. Instead, mainnet fork reproductions interact with real deployed EVM contracts, ensuring the PoC reflects actual protocol interactions and causal-chain execution for accurate vulnerability validation.