evm-audit-flow
Skill220 starsChanged 19 days agoMITView on GitHub
Use when you have a Foundry or Hardhat repository of Solidity or Vyper contracts and want the end-to-end EVM review workflow on native CLIs — a slither static pass, semgrep taint rules, mythril symbolic execution, echidna and medusa invariant fuzzing, halmos formal checks, then a forge build-and-test regression.
In this repository179 other files it gives its agents.
- AGENTS.mdAGENTS.md
- chrono/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- accessible-media-authoringSkill
- agentic-safety-auditSkill
- agent-prompt-engineeringSkill
- audio-event-map-authoringSkill
- auto-scaffoldSkill
- chain-constructSkill
- chain-construct-smart-contractSkill
- claim-verificationSkill
- code-reachability-auditSkill
- code-review-loopSkill
- color-theorySkill
- conversation-designSkill
- copy-refinementSkill
- cosmos-sdk-audit-checklistSkill
- cross-chain-bridge-auditSkill
- cross-file-relationship-synthesisSkill
- data-flow-traceSkill
- dedup-prior-art-checkSkill
- defi-invariant-checkSkill
- dependency-cycle-auditSkill
- dependency-health-triageSkill
- detection-as-codeSkill
- diff-aware-semgrep-scanSkill
- differential-reviewSkill
- dimensional-analysis-checkSkill
- dual-level-retrievalSkill
- durable-nonce-exploitationSkill
- erc1271-revert-data-checkSkill
- error-based-sstiSkill
- figma-implement-designSkill
- findings-filterSkill
- forensic-timeline-authoringSkill
- game-design-fundamentalsSkill
- game-mechanics-balancingSkill
- head-tailSkill
- incident-response-runbookSkill
- interactive-audio-designSkill
- interface-ambiguity-checkSkill
- keyword-clusteringSkill
- knowledge-base-integrationSkill
- known-advisory-backport-checkSkill
- layered-analysis-loopSkill
- level-design-patternsSkill
- locale-adaptationSkill
- multi-stance-audit-fanoutSkill
- narrative-structureSkill
- osint-platform-auditSkill
- parser-differential-route-confusionSkill
- persuasive-technical-writingSkill
- platform-complianceSkill
- player-engagement-psychologySkill
- pre-audit-threat-modelSkill
- program-rubric-lookupSkill
- read-only-reentrancy-checkSkill
- requirements-elicitationSkill
- review-severity-ladderSkill
- rule6-rights-gateSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Start from pre-audit-threat-model if an x-ray does not already exist.
- Very specific: line 17
Static analysis pass: Run slither . directly from the project root (it needs the Foundry/Hardhat build context, not a loose .sol file).
- Very specific: line 43
Symbolic execution: Run myth analyze <contract> --execution-timeout 600 on every contract flagged HIGH by step 1, plus any contract with …
- Very specific: line 55
Formal verification (critical paths only): Run halmos --function <prop> --loop <N> on high-value properties Echidna found hard to falsify …
- Very specific: line 71
Echidna coverage plateau: add a corpus dir (--corpus-dir) or switch to Medusa's coverage-from-corpus mode.
- Very specific: line 78
Do NOT report Slither medium/low findings without confirming exploitability via a call sequence or myth evidence.
- Distinctive: line 80
Do NOT run Echidna/Medusa without invariant tests — property-less fuzzing yields nothing.
- Very specific: line 81
Do NOT run myth on a proxy without resolving the implementation first.
- Distinctive: line 82
Do NOT skip Slither for "simple" contracts — over half of historical EVM findings are in contracts under 200 lines.
- Very specific: line 84
Do NOT invoke any dead tool_wrappers/* name (slither_scan, mythril_analyze, echidna_fuzz, halmos_check, forge_test).
- Very specific: line 87
Do NOT route through the retired guarded-slither / guarded-semgrep MCPs (Trail of Bits mcp-context-protector wrappers, removed from both …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
evm-audit-flow
Stateful EVM audit pipeline from raw contract source through confirmed-finding delivery. Use
when you have a Foundry or Hardhat project with Solidity/Vyper contracts. Every step runs a
native host CLI (slither, semgrep, myth, echidna/medusa, halmos, forge) invoked
directly; there is no MCP wrapper in front of them, no tool_wrappers layer, and no retired KG.
Start from pre-audit-threat-model if an x-ray does not already exist.
Order of ops
- Static analysis pass. Run
slither .directly from the project root (it needs the Foundry/Hardhat build context, not a loose.solfile).slither . --json -gives structured output,slither --list-detectorsenumerates detectors, andslither . --print function-summarygives per-function context. Classify detectors: HIGH-signal (reentrancy-eth,arbitrary-send,controlled-delegatecall,suicidal,unprotected-upgrade) vs NOISE (naming-convention, too-many-digits, solc-version). Do NOT dismissreentrancy-ethas a false positive without tracing the call stack.solc-selectis available for pinning the compiler, but do not pass--always-install(no silent network downloads); confirm the version is already present. Pattern/taint pass (the static analog of symbolic execution). Run project-specific Semgrep rules with the
semgrepCLI directly —semgrep scan --config <rules.yaml> --metrics=off --json <path>— taint sources = external/msg.sender-reachable inputs, sinks = value transfers,delegatecall, storage writes. Author rules withsemgrep-rule-author; a reachable sink with no realized impact is a lead, not a finding. Local rule files need no login.A zero is not a clean scan until the same rule has fired on a known positive. Two measured ways to get an empty result (2026-10-27, semgrep 1.157.0): a rule file that fails YAML parsing exits 7 and reports the error only in the JSON
errorsarray with an emptyresultslist (an unquoted pattern containing{or:is the usual cause — quote it:pattern: "$X.call{value: $V}($A)"fires, the unquoted form does not parse); and a pattern that does not match the call shape —$X.call(...)missesto.call{value: 1}("")— returns zero findings, zero errors, exit 0. Check the exit code,errors, and the positive control before believing a zero.- Symbolic execution. Run
myth analyze <contract> --execution-timeout 600on every contract flagged HIGH by step 1, plus any contract with external calls,delegatecall, orselfdestruct. Surface: integer overflow, unchecked return values,tx.originaccess-control bypass, ether-locking. For proxies, resolve the implementation address first —mythcannot followdelegatecallto a separate contract by default. - Invariant authoring + fuzzing. Author/refresh Echidna or Medusa invariants (token
conservation, access-control, CEI reentrancy) in
test/invariants/. Runechidna . --contract <Test> --config echidna.yamlfor an initial pass; if coverage plateaus switch tomedusa fuzz --config medusa.json(coverage-guided). For DeFi, applydefi-invariant-check. Minimum meaningful campaign: 30 minutes. - Formal verification (critical paths only). Run
halmos --function <prop> --loop <N>on high-value properties Echidna found hard to falsify in bounded time. Halmos gives unbounded symbolic verification for simpler properties; do not throw the whole suite at it (it times out on complex state machines or unbounded loops). - Lint + compile regression.
forge build(orsolcon modified contracts) to confirm no compilation regression;forge fmt --checkfor style. - Final test run.
forge testto confirm the suite passes; record any new failure.
When to pivot
- Slither false-positive flood: narrow with
--detect <high-signal list>and add a.slither.config.jsonsuppression for known project FPs. mythtimes out on complex contracts:--execution-timeout 300 --create-timeout 60, and focus on functions with external calls and value transfers.- Echidna coverage plateau: add a corpus dir (
--corpus-dir) or switch to Medusa's coverage-from-corpus mode. - Halmos timeouts on loop-heavy code: bound with
--loop; Halmos is not for unbounded loops.
Anti-patterns
- Do NOT report Slither medium/low findings without confirming exploitability via a call
sequence or
mythevidence. - Do NOT run Echidna/Medusa without invariant tests — property-less fuzzing yields nothing.
- Do NOT run
mython a proxy without resolving the implementation first. - Do NOT skip Slither for "simple" contracts — over half of historical EVM findings are in contracts under 200 lines.
- Do NOT invoke any dead
tool_wrappers/*name (slither_scan,mythril_analyze,echidna_fuzz,halmos_check,forge_test); those wrap a container library that no longer exists — use the native CLIs above. - Do NOT route through the retired
guarded-slither/guarded-semgrepMCPs (Trail of Bits mcp-context-protector wrappers, removed from both lanes on 2026-10-27, commit02442bdc); their tool names (run_detectors,semgrep_scan_with_custom_rule) no longer resolve — run the CLIs above.
Example
# Step 1: static analysis (native)
slither . --exclude naming-convention,solc-version
# Step 2: taint rules (native) -- run the same rule on a known positive first
semgrep scan --config rules/evm-taint.yaml --metrics=off --json src/
# Step 3: symbolic execution on a flagged contract
myth analyze src/Vault.sol --execution-timeout 600
# Step 4: fuzzing (30-min minimum for DeFi)
echidna . --contract InvariantTest --config echidna.yaml --test-limit 500000
# Step 7: final test run
forge testRecording (chrono-vault)
The task packet's injected memory contract owns the exact call shape, sequence, and fields - see
wirework-reflect. Do not copy a record(...) example or add fields (including source_task) from
memory; the server binds them, and a baked example violates the run's authenticated schema. Memory is
best-effort telemetry and never gates the work. What is worth recording here is the task-specific
outcome: finding counts by severity, invariant violations, tools run.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

