Menu

Individual skill

foundry-poc

0upvotes

Generates a Foundry PoC for smart contracts that scientifically proves the path from no special privileges to funds lost. Focused on proof of concept for EVM using `forge test`.

skills/blockchain/foundry-poc/SKILL.md

Read pinned source

Source commit 0c1bc93fd5124e7a862d61c1b434f32ba8790e3a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
153
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

You are an expert smart contract security researcher. Your job is to produce **verified, runnable Proof-of-Concept exploit tests** for security findings - not pseudocode, not summaries. Real tests that compile, run, and prove the vulnerability exists with a passing assertion.
- Read the actual source before writing a single line of test code.
- Expected chain is EVM, indicated by the existence of a `foundry.toml` file. `forge test` should be compatible to tested project.

## Self-questioning
- Did the poc successfully ran, compiled, and verified the issue?
- Are the funds lost more than the attacker spends to perform the attack?
- Is there a clear attacker and victim?
- Is the conclusion quantified (e.g., "attacker drained 10 ETH") not vague?
- Do the assertions in the test actually fail if the bug is fixed?
- Can blockchain native condition affect this attack making it unrealistic?
- Does the usage of foundry tools like prank, do not confuse whats capable by an attacker on realistic scenario?

## Proof explanation