Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add PaulRBerg/foundry-template --skill foundry-testinggit clone --depth 1 https://github.com/PaulRBerg/foundry-templateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/paulrberg/foundry-template/foundry-testing)<a href="https://agentmods.dev/skills/paulrberg/foundry-template/foundry-testing"><img src="https://agentmods.dev/badge/skills/paulrberg/foundry-template/foundry-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/paulrberg/foundry-template/foundry-testing"><img src="https://agentmods.dev/badge/skills/paulrberg/foundry-template/foundry-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00064 | $0.02090 |
| Opus 5.5 | $0.00026 | $0.00836 |
| Sonnet 5.5 | $0.00013 | $0.00418 |
| Haiku 4.5 | $0.00006 | $0.00209 |
Grade A, and why
foundry-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 21d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Foundry Testing
Write Foundry tests and scripts that pass, pin down the specified behavior, and follow the project's conventions.
Ground Rules
- Read
foundry.toml(testandscriptdirectories, fuzz runs, profiles,block_timestamp),remappings.txt, the nearestAGENTS.md, and one or two neighboring tests before writing. Existing layout, base contracts, and helpers win over the defaults below. - Import Forge Std through the project's remapping; in this template that is
forge-std/src/Test.sol. - Keep tests deterministic: derive times from
block.timestamp, which this template pins infoundry.toml, and pin fork block numbers.
References
- references/btt.md: read before writing or changing a
.treespec or a BTT-generated test. - references/cheat-codes.md: read when using
vmcheatcodes or Forge Std helpers beyondprank,warp, andexpectRevert. - references/test-infrastructure.md: read when a suite outgrows one file and needs a shared base test, users, constants, defaults, modifiers, mocks, or revert helpers.
- references/invariant-patterns.md: read when writing invariant tests, handlers, or stores.
- references/gas-benchmarking.md: read when measuring, snapshotting, or comparing gas.
Test Types
| Type | Function prefix | Location in larger suites |
|---|---|---|
| Concrete (unit) | test_ |
tests/integration/concrete/ |
| Fuzz | testFuzz_ |
tests/integration/fuzz/ |
| Fork | testFork_ (or testForkFuzz_ if fuzzed) |
tests/fork/ |
| Invariant | invariant_ |
tests/invariant/ |
| Deployment scripts | run |
script/*.s.sol |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 21d ago First seen · 152 lines · 64 tokens per session scan A ff7c26ad9b1d
foundry-testing is a skill published in the GitHub repository PaulRBerg/foundry-template (642 stars, last pushed 7d ago), licensed MIT. It adds 64 tokens to every session and 2,090 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-25.
Other skills, from other repositories
Smart Contract Testing
Smart contract testing with Hardhat, Foundry, and Brownie including unit tests, gas optimization, reentrancy checks, and fork testing.
tevm
Build, simulate, test, fork, and debug EVM transactions in TypeScript with tevm 1.0.0-rc.151. Use for in-process EVM scripts, typed Solidity imports, lazy mainnet or OP-stack forks, direct account and storage setup, viem-compatible contract actions, Vitest EVM tests, traces, and transaction simulation.
blockchain-expert
Expert-level blockchain, Web3, smart contracts, DeFi, and cryptocurrency development. Use when the user mentions Web3, smart contracts, DeFi, Ethereum, or Solidity, or when the task involves Blockchain Fundamentals, Web3 & DeFi, Smart Contract Security, or Gas Optimization.
web3-expert
Build production-ready Web3 applications including smart contracts, dApps, DeFi protocols, and decentralized storage solutions. Use when the user mentions Web3, smart contracts or Solidity, dApps, DeFi protocols, ethers.js or web3.js, IPFS, or on-chain integration with Ethereum-compatible networks.
ethereum-development
Production-grade Ethereum/EVM development workflow for smart contracts, dApps, transactions, clients, gas optimization, testing, security review, deployment, verification, monitoring, and incident response across Foundry, Hardhat, Solidity, TypeScript, viem, ethers, wagmi, and common EVM networks.
solidity-language-docs
Solidity 0.8.36 — smart contracts, types, functions, modifiers, events, inheritance, libraries, assembly, ABI.