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 sablier-labs/plugin-marketplace --skill foundrygit clone --depth 1 https://github.com/sablier-labs/plugin-marketplaceWrote 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/sablier-labs/plugin-marketplace/foundry)<a href="https://agentmods.dev/skills/sablier-labs/plugin-marketplace/foundry"><img src="https://agentmods.dev/badge/skills/sablier-labs/plugin-marketplace/foundry/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/sablier-labs/plugin-marketplace/foundry"><img src="https://agentmods.dev/badge/skills/sablier-labs/plugin-marketplace/foundry.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.00049 | $0.01917 |
| Opus 5.5 | $0.00020 | $0.00767 |
| Sonnet 5.5 | $0.00010 | $0.00383 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
foundry 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 1mo 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.
This is a copy
97% identical to cli-forge — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Foundry Testing & Script Skill
Rules and patterns for Foundry tests. Find examples in the actual codebase.
Bundled References
| Reference | Content | When to Read |
|---|---|---|
./references/test-infrastructure.md |
Constants, defaults, mocks | When setting up tests |
./references/cheat-codes.md |
Common cheatcode patterns | When using vm cheatcodes |
./references/invariant-patterns.md |
Handlers, stores, invariants | When writing invariant tests |
./references/formal-verification.md |
Halmos, Certora, symbolic exec | When proving correctness |
./references/deployment-scripts.md |
Script patterns, verification | When writing deploy scripts |
./references/deployment-checklist.md |
Pre-mainnet deployment steps | Before deploying to production |
./references/gas-benchmarking.md |
Snapshot, profiling, CI | When measuring gas performance |
./references/sablier-conventions.md |
Sablier-specific patterns | When working in Sablier repos |
Test Types
| Type | Directory | Naming | Purpose |
|---|---|---|---|
| Integration | tests/integration/concrete/ |
*.t.sol |
BTT-based concrete tests |
| Fuzz | tests/integration/fuzz/ |
*.t.sol |
Property-based testing |
| Fork | tests/fork/ |
*.t.sol |
Mainnet state testing |
| Invariant | tests/invariant/ |
Invariant*.t.sol |
Stateful protocol properties |
| Scripts | scripts/solidity/ |
*.s.sol |
Deployment/initialization |
What ships with it
8 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.
- references/cheat-codes.md 3.2 KB
- references/deployment-checklist.md 5.5 KB
- references/deployment-scripts.md 5.0 KB
- references/formal-verification.md 7.3 KB
- references/gas-benchmarking.md 6.3 KB
- references/invariant-patterns.md 6.6 KB
- references/sablier-conventions.md 5.4 KB
- references/test-infrastructure.md 4.0 KB
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.
- 1mo ago First seen · 240 lines · 49 tokens per session scan A febb52b6c228
foundry is a skill published in the GitHub repository sablier-labs/plugin-marketplace (7 stars, last pushed 13d ago), licensed MIT. It adds 49 tokens to every session and 1,917 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to cli-forge, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
building-pydantic-ai-agents
Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), workspaces, structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydanticai, or asks to build an AI agent, add tools/capabilities, attach a workspace, defer capability…
fizz
Generate Echidna/Medusa-compatible Solidity fuzz suites from Foundry or Hardhat projects. Trigger on "fizz", "generate fuzz suite", "build fuzz harness", "stateful fuzzing", "fuzzing harness", "property testing", and "invariant suite".
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
software-test-creation
Write failing tests for a TDD slice based on acceptance criteria and codebase conventions. Use when the "red" phase of red-green-refactor requires tests that define expected behavior before implementation exists. Discovers codebase test conventions first, writes test files that compile or parse but fail because the…
foundry-testing
Write and debug Foundry tests and Solidity scripts. Use when writing unit, fuzz, fork, or invariant tests, writing bulloak BTT .tree specs (Branching Tree Technique), using cheatcodes, benchmarking gas, measuring coverage, writing deploy scripts, or working in tests/ or script/.