Web3 Testing (Foundry primary, Hardhat 3 supported)

Routing-first skill. The body is intentionally thin; depth lives in reference/. Open only the files you actually need.

Token economy rules for the agent

Read these before doing anything else. They cut answer cost without losing quality.

1. Do not paste the user's contract back at them. Reference function names and line ranges; write only the test harness or the diff.
2. Read at most 2 reference files per turn. Use the routing table to pick.
3. Never reproduce forge-std internals. Reference them by name (Test, StdInvariant, StdCheats) and assume the user has forge-std installed.
4. Default to Foundry in examples. Only show Hardhat when the user says Hardhat or already has a Hardhat project.
5. Prefer tables over prose for cheatcode catalogs, option matrices, or revert-parsing rules.
6. Verify version-specific APIs via Context7 for Foundry, Hardhat, OpenZeppelin, Slither, Echidna, Halmos, and ethers/viem. Foundry and Hardhat both moved fast through 2024-2026; treat any pre-2026 snippet in your training as suspect -- especially testFail*, ethers v5, Goerli, and Hardhat 2 ESM assumptions.

Routing table