Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ccashwell/evm-cortexnpx agentmods add skills/ccashwell/evm-cortex/test-fixturesWrote 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/ccashwell/evm-cortex/test-fixtures)<a href="https://agentmods.dev/skills/ccashwell/evm-cortex/test-fixtures"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/test-fixtures.svg" alt="Measured on agentmods" 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.00037 | $0.01926 |
| Opus 5 | $0.00018 | $0.00963 |
| Sonnet 5 | $0.00007 | $0.00385 |
| Haiku 4.5 | $0.00004 | $0.00193 |
Grade A, and why
test-fixtures 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 3d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Fixtures & Helpers
Base Test Contract
Shared setUp that all test files inherit:
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;
import {Test} from "forge-std/Test.sol";
import {IERC20} from "@openzeppelin/contracts/token/ERC20/IERC20.sol";
abstract contract BaseTest is Test {
address public alice;
address public bob;
address public carol;
address public deployer;
address public treasury;
function setUp() public virtual {
alice = makeAddr("alice");
bob = makeAddr("bob");
carol = makeAddr("carol");
deployer = makeAddr("deployer");
treasury = makeAddr("treasury");
vm.deal(alice, 100 ether);
vm.deal(bob, 100 ether);
vm.deal(carol, 100 ether);
}
function _labelAll() internal {
vm.label(alice, "Alice");
vm.label(bob, "Bob");
vm.label(carol, "Carol");
vm.label(deployer, "Deployer");
vm.label(treasury, "Treasury");
}
function _fundToken(address token, address to, uint256 amount) internal {
deal(token, to, amount);
}
function _approveToken(address token, address owner, address spender, uint256 amount) internal {
vm.prank(owner);
IERC20(token).approve(spender, amount);
}
}
Mock ERC20 Token
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;
import {ERC20} from "@openzeppelin/contracts/token/ERC20/ERC20.sol";
contract MockERC20 is ERC20 {
uint8 private _decimals;
constructor(string memory name, string memory symbol, uint8 decimals_)
ERC20(name, symbol)
{
_decimals = decimals_;
}
function decimals() public view override returns (uint8) {
return _decimals;
}
function mint(address to, uint256 amount) external {
_mint(to, amount);
}
function burn(address from, uint256 amount) external {
_burn(from, amount);
}
}
Token Fixture Library
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;
import {MockERC20} from "./MockERC20.sol";
library TokenFixtures {
function deployUSDC() internal returns (MockERC20) {
return new MockERC20("USD Coin", "USDC", 6);
}
function deployWETH() internal returns (MockERC20) {
return new MockERC20("Wrapped Ether", "WETH", 18);
}
function deployDAI() internal returns (MockERC20) {
return new MockERC20("Dai Stablecoin", "DAI", 18);
}
function deployWithDecimals(uint8 decimals) internal returns (MockERC20) {
return new MockERC20("Test Token", "TEST", decimals);
}
}
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.
- 3d ago First seen · 285 lines · 37 tokens per session scan A bf18bb9ff7c7
test-fixtures is a skill published in the GitHub repository ccashwell/evm-cortex (127 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,926 once invoked, about $0.0002 per session on Opus 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-03.
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.
smart-contract-testing
Guide for testing smart contracts using Foundry and Hardhat, covering unit tests, fuzz testing, invariant testing, fork testing, and gas benchmarking.
cairo-testing
Cairo smart-contract testing with snforge. Trigger on "write tests", "add unit tests", "fuzz test", "integration test", "test this contract", "regression test". Guides test strategy, cheatcode usage, and coverage.
verification-protocol
How to prove a hypothesis is TRUE or FALSE using Move unit tests.
foundry-solidity
Build and test Solidity smart contracts with Foundry toolkit. Use when developing Ethereum contracts, writing Forge tests, deploying with scripts, or debugging with Cast/Anvil. Triggers on Foundry commands (forge, cast, anvil), Solidity testing, smart contract development, or files like foundry.toml, .t.sol, .s.sol.
blockchain-testing
Use this skill when asked about testing smart contracts, Foundry tests, Hardhat tests, fuzz testing, invariant testing, property-based testing, formal verification, audit preparation, integration testing for dApps, and blockchain testing patterns. Covers Foundry cheatcodes, Echidna fuzzing, Certora verification…