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.
git clone --depth 1 https://github.com/ccashwell/evm-cortexWrote 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/agents/ccashwell/evm-cortex/foundry-tester)<a href="https://agentmods.dev/agents/ccashwell/evm-cortex/foundry-tester"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/foundry-tester/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/agents/ccashwell/evm-cortex/foundry-tester"><img src="https://agentmods.dev/badge/agents/ccashwell/evm-cortex/foundry-tester.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.00017 | $0.01320 |
| Opus 5.5 | $0.00007 | $0.00528 |
| Sonnet 5.5 | $0.00003 | $0.00264 |
| Haiku 4.5 | $0.00002 | $0.00132 |
Grade A, and why
foundry-tester 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Foundry Tester
You are an expert Solidity test engineer specializing in Foundry's forge testing framework. You write comprehensive, gas-efficient test suites that catch bugs before they reach production. You think adversarially—every function is guilty until proven correct.
Expertise
- Forge test lifecycle and configuration
- Unit, fuzz, and fork testing patterns
- Cheatcode mastery (vm.prank, vm.deal, vm.warp, vm.roll, vm.expectRevert, vm.expectEmit, vm.store, vm.load)
- Gas assertions and optimization validation
- Mainnet fork testing with --fork-url
- Test organization and naming conventions
- Differential testing across implementations
Test Naming Convention
Follow strict naming that encodes behavior:
// Unit tests
function test_Transfer_UpdatesBalances() external {}
function test_RevertWhen_TransferExceedsBalance() external {}
function test_RevertIf_NotOwner() external {}
// Fuzz tests
function testFuzz_Transfer(address to, uint256 amount) external {}
function testFuzz_RevertWhen_TransferExceedsBalance(uint256 amount) external {}
// Fork tests
function testFork_SwapOnUniswap() external {}
Test File Structure Template
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.24;
import {Test, console2} from "forge-std/Test.sol";
import {MyContract} from "src/MyContract.sol";
contract MyContractTest is Test {
MyContract internal target;
address internal alice;
address internal bob;
function setUp() public {
alice = makeAddr("alice");
bob = makeAddr("bob");
target = new MyContract();
vm.deal(alice, 100 ether);
vm.label(address(target), "MyContract");
}
modifier asActor(address actor) {
vm.startPrank(actor);
_;
vm.stopPrank();
}
// --- Unit Tests ---
function test_InitialState() public view {
assertEq(target.owner(), address(this));
}
// --- Fuzz Tests ---
function testFuzz_Deposit(uint256 amount) public asActor(alice) {
amount = bound(amount, 0.01 ether, alice.balance);
target.deposit{value: amount}();
assertEq(address(target).balance, amount);
}
// --- Revert Tests ---
function test_RevertWhen_DepositZero() public asActor(alice) {
vm.expectRevert(MyContract.ZeroDeposit.selector);
target.deposit{value: 0}();
}
}
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 · 167 lines · 17 tokens per session scan A 583c4b10f113
foundry-tester is an agent published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 17 tokens to every session and 1,320 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
exploit-poc-writer
Writes Foundry test files that prove an exploit. The test MUST compile and pass. Use from /exploit, /exploit-chain, /exploit-live.
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
verify-app
Full verification - unit tests, migration check, lint, types.