Foundry POC Mainnet Fork — Development skill for Claude Code
Claude Code skill that produces submission-ready Foundry PoCs against mainnet-forked deployed contracts.
How to install Foundry POC Mainnet Fork
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open cholakovvv/foundry-poc-mainnet-fork and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Foundry POC Mainnet Fork does
Claude Code skill that produces submission-ready Foundry PoCs against mainnet-forked deployed contracts.
Alternatives in Development
- Competitive Battlecard — Create sales-ready battlecards against specific competitors 7.8k ★
- /report — Generate a submission-ready bug bounty report 1.8k ★
- Axiom Marketplace Submission Guide — Axiom Marketplace Submission Guide skill 834 ★
README
foundry-poc-mainnet-fork
A [Claude Code](https://docs.claude.com/en/docs/claude-code/overview) skill that turns a smart contract vulnerability finding into a submission-ready Foundry PoC that forks mainnet and exercises real deployed contracts end-to-end.
Built and validated by [@cholakovvv](https://x.com/cholakovvv) across four production bounty findings spanning freeze, routing DoS, and pool-drain theft shapes.
What It Does
Given a vulnerability description and the deployed addresses of the affected protocol, the skill produces a single Foundry test file that:
- Forks mainnet (or any EVM chain) at a block where the bug is reachable
- Binds every protocol contract as a
constantreal address - Executes the full causal chain from the action that first triggers the vulnerable state to the final realized impact
- Ends with assertions that encode the vulnerability's end-state (balance deltas for theft, reverts for DoS, quantified stranding for freeze)
- Passes
forge test -vvvvon the first try, or flags a blocker with a concrete reason
No mocks. No minimal reimplementations. No `vm.store` shortcuts around protocol pipelines unless explicitly documented.
Who This Is For
Smart contract security researchers working on bug bounty platforms or audits who want to produce a clean mainnet-fork PoC without spending 2 hours on boilerplate and address-hunting. The skill takes care of:
- Classification of the finding (frozen historical vs forward-looking risk vs both)
- Identifying the first-triggering action in the causal chain
- Finding real deployed addresses when the user provides partial info
- Writing interfaces that match deployed bytecode
- End-to-end test structure with labeled balance deltas
Requirements
- Claude Code with a Claude Sonnet 4.5 or Claude Opus 4.5+ subscription (or API access)
- Foundry installed (
forge,cast) - An EVM RPC URL (free Alchemy, Infura, drpc.org, mevblocker.io all work)
Installation
cd ~/.claude/skills
Related Skills
Economic Sim
Quantify a candidate economic finding — compute attack cost vs extractable value and, when possible, reproduce
Fde Simulation
Hands-on Forward Deployed Engineer role simulations: scope an enterprise engagement, build multi-agent prototy
Rcode Upgrade
Upgrade a R.Code-managed project's deployed rails to the current global framework version. Compares .rcode/con
Zp Report
Draft a submission-ready report from a verified finding. Never submits. Usage: /zp-report
Brief Compliance Check
Check a LaTeX coursework submission against the requirements in a supplied
Peer Review Check
Author self-check of a manuscript draft against Elsevier's structured peer review prompts, before submission —
Related Agents
Submit Checker
Use when the user wants to check whether a paper is ready for submission to a specific journal. Produces a sub
Vuln Discloser
Re-verifies confirmed findings against the latest upstream release and drafts maintainer-ready security adviso
Security Verifier
You write and execute PoC tests to PROVE bugs exist. Read the VERIFICATION_PROTOCOL skill for your language's