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 ccashwell/evm-cortex --skill fizzgit 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/skills/ccashwell/evm-cortex/fizz)<a href="https://agentmods.dev/skills/ccashwell/evm-cortex/fizz"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/fizz/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/ccashwell/evm-cortex/fizz"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/fizz.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.00060 | $0.10931 |
| Opus 5.5 | $0.00024 | $0.04372 |
| Sonnet 5.5 | $0.00012 | $0.02186 |
| Haiku 4.5 | $0.00006 | $0.01093 |
Grade A, and why
fizz scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf https://raw.githubusercontent.com/pashov/skills/main/fizz/VERSION This is a copy
98% identical to fizz — 28 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 — 605 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fizz
Generate a stateful Solidity fuzz suite under {SUITE_DIR} (default: test/fizz/), with metadata and fuzzer runtime files under {META_DIR} (default: fizz_data/).
Use Echidna and Medusa for invariant campaigns. Use Foundry for compilation, smoke testing, and quick debugging.
Vendored from the Pashov Audit Group's open-source approach (github.com/pashov/skills), skill fizz, VERSION 1 (see the VERSION file alongside this one). The scripts/, templates/, references/, and agents/ directories are upstream code carried over intact; the only local adaptations are the x-ray acquisition path in Step 3 (EVM Cortex ships the methodology as the xray-pre-audit skill) and the companion-skill locations noted below. Check for a newer upstream revision before relying on this:
curl -sf https://raw.githubusercontent.com/pashov/skills/main/fizz/VERSION
Relationship to other EVM Cortex skills
| Skill | Relationship |
|---|---|
xray-pre-audit |
Produces the x-ray/x-ray.md protocol understanding that Step 3 consumes. Run it first — the fallback Protocol Analyzer is strictly worse input for invariant discovery. |
fizz-sync |
Re-use entry point. After source changes, run it instead of regenerating the suite. |
fizz-convert |
Turns plain-English properties added to PROPERTIES.md into Solidity assertions. |
invariant-testing, fuzzing-patterns |
Reference material for hand-writing or reviewing properties and handlers outside this pipeline. |
pashov-audit-pipeline |
Complementary, not overlapping — that pipeline reasons about attack paths, this one drives a fuzzer at the state space. A violated SHOULD-HOLD property here is strong input to a finding there. |
Workflow Rules
- Follow the steps in order. Do not skip forward if a required artifact for the current step does not exist yet.
- If a step fails, stop there and report the blocker.
- If tooling is missing, say exactly what was attempted and what is missing.
- Keep the generated Solidity suite isolated under
test/fizz/and the metadata/runtime files underfizz_data/unless the user explicitly asks for different paths. - Reuse existing project setup and test logic whenever possible; do not invent a deployment flow if the repo already has one.
What ships with it
47 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.
- agents/implementers/global-property-implementer.md 4.0 KB
- agents/implementers/specific-property-implementer.md 5.3 KB
- agents/invariant-discovery/adversarial-profit-maximizer.md 6.5 KB
- agents/invariant-discovery/conservation-auditor.md 4.9 KB
- agents/invariant-discovery/protocol-type-specialist.md 8.3 KB
- agents/invariant-discovery/roundtrip-rounding-analyst.md 7.5 KB
- agents/invariant-discovery/state-transition-mapper.md 4.5 KB
- agents/invariant-discovery/synthesizer.md 15 KB
- agents/protocol-analyzer.md 5.5 KB
- agents/report-writer.md 8.6 KB
- references/handler-patterns.md 10.0 KB
- references/property-generation.md 5.4 KB
- references/selection-policy.md 2.2 KB
- references/setup-playbook.md 3.7 KB
- references/template-map.md 7.1 KB
- scripts/ensure_foundry.sh 4.3 KB runs code
- scripts/estimate_cost.js 6.1 KB runs code
- scripts/extract_abis.js 11 KB runs code
- scripts/fizz_sync.js 28 KB runs code
- scripts/generate_handlers.js 14 KB runs code
- scripts/generate_suite.js 9.5 KB runs code
- scripts/lib/log-viewer.js 11 KB runs code
- scripts/run_echidna.js 6.3 KB runs code
- scripts/run_medusa.js 12 KB runs code
- scripts/select_functions.js 23 KB runs code
- scripts/setup_fuzz_profile.sh 4.9 KB runs code
- templates/Actor.sol 2.0 KB
- templates/Base.sol 4.6 KB
- templates/echidna.yaml 599 B
- templates/FoundryTester.sol 949 B
- templates/FuzzTester.sol 245 B
- templates/handlers/Handlers.sol 413 B
- templates/medusa.json 2.1 KB
- templates/Properties.sol 886 B
- templates/README.md 2.1 KB
- templates/Snapshots.sol 618 B
- templates/utils/Clamp.sol 7.4 KB
- templates/utils/DecimalPrinter.sol 1.8 KB
- templates/utils/Deployer.sol 530 B
- templates/utils/EnumerableSet.sol 5.9 KB
- templates/utils/Hevm.sol 2.2 KB
- templates/utils/Logger.sol 14 KB
- templates/utils/Math.sol 1.7 KB
- templates/utils/MockERC20.sol 10 KB
- templates/utils/PropertiesAsserts.sol 7.3 KB
- templates/utils/StringUtils.sol 3.4 KB
- VERSION 2 B
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 · 605 lines · 60 tokens per session scan A 50e92f39387d
fizz is a skill published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 60 tokens to every session and 10,931 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 98% identical to fizz, differing in 28 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…
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…
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".
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/.
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…