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 fizz-syncgit 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-sync)<a href="https://agentmods.dev/skills/ccashwell/evm-cortex/fizz-sync"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/fizz-sync/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-sync"><img src="https://agentmods.dev/badge/skills/ccashwell/evm-cortex/fizz-sync.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.00077 | $0.03699 |
| Opus 5.5 | $0.00031 | $0.01480 |
| Sonnet 5.5 | $0.00015 | $0.00740 |
| Haiku 4.5 | $0.00008 | $0.00370 |
Grade A, and why
fizz-sync 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
100% identical to fizz-sync — 10 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fizz Sync Skill — fizz-sync
Reconcile a project previously processed by the Fizz skill with a changed source tree. This is the re-use entry point: after the user modifies Solidity sources, fizz-sync detects drift, quarantines stale properties, regenerates drifted handler stubs, and refreshes the snapshot — WITHOUT re-running the full 11-step pipeline.
When to use
- The source contracts under
src/changed sincefizzlast ran. - A property in
PROPERTIES.mdfails to compile or references a function that no longer exists. - The user added new external functions they want fuzzed.
- The user wants a "is anything stale?" health check before re-running a campaign.
Parameters
SUITE_DIR: Solidity suite directory relative to project root (default:test/fizz). Use the same value that was passed to thefizzskill when the harness was generated.META_DIR: Metadata directory relative to project root (default:fizz_data). Use the same value that was passed to thefizzskill.
Arguments
--init— one-time bootstrap: create{META_DIR}/last-run.jsonfrom the current state. Use this the first time fizz-sync runs on a project (or when adopting fizz-sync on a project that was fuzzed before the snapshot format existed).--only <Contract>— scope the sync to a single contract name.--apply— actually perform the automatic fixes. Without--apply, fizz-sync runs in dry-run mode and only reports drift.--no-property-quarantine— skip the property quarantine phase (useful if the user wants to handle stale properties manually).
The default (no flags) runs a dry-run drift report.
Preconditions
- The project must have been processed by the
fizzskill at least once. Look for:{PROJECT_ROOT}/{META_DIR}/contracts.json{PROJECT_ROOT}/{META_DIR}/entry-point-selection.json{PROJECT_ROOT}/{SUITE_DIR}/(suite directory)
- If any of the above are missing, stop and tell the user to run
fizzfirst.
STEP 0: REBUILD CURRENT ABIS
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 · 329 lines · 77 tokens per session scan A 5b39aecc3db0
fizz-sync is a skill published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 77 tokens to every session and 3,699 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to fizz-sync, differing in 10 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…