New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Evm Audit Flow

by mtarcure in mtarcure/claude-vibe-squad

A skill your agent uses 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…

MITAuto-check passedSecurity

Install Evm Audit Flow

skills CLI
$ npx skills add mtarcure/claude-vibe-squad --skill evm-audit-flow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mtarcure/claude-vibe-squad evm-audit-flow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/evm-audit-flow .claude/skills/evm-audit-flow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
evm-audit-flow
GitHub stars
164
Token cost
~1.5k tokens
SKILL.md length
666 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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…

  • Works in 7 steps: Static analysis pass. Run slither . (or… → Pattern/taint pass (the static analog of… → Symbolic execution. Run myth analyze… → …
  • You have a Foundry
  • SKILL.md covers Order of ops, When to pivot, Anti-patterns and Example, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Evm Audit Flow is an agent skill from mtarcure/claude-vibe-squad. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Security, covering Smart contracts and Static analysis and SAST. It works with Semgrep, Solidity and Model Context Protocol. The repository describes itself as: Multi-model AI orchestration where behaviour is Markdown, not code. One coordinator routes scoped task packets to 71 role-based specialists across 5 model families (Codex /… The licence is MIT.

When your agent uses it

  • You have a Foundry
  • Hardhat repository of Solidity
  • Vyper contracts and want the end-to-end EVM review workflow on native CLIs — a slither static pass
  • Semgrep taint rules

Example prompts

  • “/evm-audit-flow”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Static analysis pass. Run slither . (or the guarded-slither MCP for structured,
  2. Pattern/taint pass (the static analog of symbolic execution). Run project-specific
  3. Symbolic execution. Run myth analyze --execution-timeout 600 on every
  4. Invariant authoring + fuzzing. Author/refresh Echidna or Medusa invariants (token
  5. Formal verification (critical paths only). Run halmos --function --loop on
  6. Lint + compile regression. forge build (or solc on modified contracts) to confirm
  7. Final test run. forge test to confirm the suite passes; record any new failure.

What it can do on your machine

Read from SKILL.md and the folder at commit 7bd69f8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Evm Audit Flow loads about 1.5k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 666 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mtarcure/claude-vibe-squad at commit 7bd69f8, republished under its MIT licence (© mtarcure). 666 words, ~1,496 tokens.

Download SKILL.mdSave it as .claude/skills/evm-audit-flow/SKILL.md (or your agent's skills folder).
name
evm-audit-flow
description
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.
audience
specialist

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 or a guarded MCP (guarded-slither, guarded-semgrep — Trail-of-Bits mcp-context-protector, schema-pinned and fail-closed); there is 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

  1. Static analysis pass. Run slither . (or the guarded-slither MCP for structured, fail-closed queries — list_detectors, run_detectors, get_function_source). Classify detectors: HIGH-signal (reentrancy-eth, arbitrary-send, controlled-delegatecall, suicidal, unprotected-upgrade) vs NOISE (naming-convention, too-many-digits, solc-version). Do NOT dismiss reentrancy-eth as a false positive without tracing the call stack. solc-select is available for pinning the compiler, but do not pass --always-install (no silent network downloads); confirm the version is already present.

  2. Pattern/taint pass (the static analog of symbolic execution). Run project-specific Semgrep rules via the guarded-semgrep MCP (semgrep_scan_with_custom_rule) — taint sources = external/msg.sender-reachable inputs, sinks = value transfers, delegatecall, storage writes. Author rules with semgrep-rule-author; a reachable sink with no realized impact is a lead, not a finding.

    Pass code_files[].path as a RELATIVE path. An absolute path is rejected with Untrusted path must be relative. The sibling tool semgrep_scan takes the opposite convention (absolute only) and then fails anyway -- it fetches its ruleset from the registry and 401s -- so treat semgrep_scan_with_custom_rule as the only working MCP entry point, with the semgrep CLI as the fallback. Both failure modes return an empty result that reads as a clean scan, so confirm your rule fires on a known positive before believing a zero. (Measured 2026-08-02.)

  3. Symbolic execution. Run myth analyze <contract> --execution-timeout 600 on every contract flagged HIGH by step 1, plus any contract with external calls, delegatecall, or selfdestruct. Surface: integer overflow, unchecked return values, tx.origin access-control bypass, ether-locking. For proxies, resolve the implementation address first — myth cannot follow delegatecall to a separate contract by default.

  4. Invariant authoring + fuzzing. Author/refresh Echidna or Medusa invariants (token conservation, access-control, CEI reentrancy) in test/invariants/. Run echidna . --contract <Test> --config echidna.yaml for an initial pass; if coverage plateaus switch to medusa fuzz --config medusa.json (coverage-guided). For DeFi, apply defi-invariant-check. Minimum meaningful campaign: 30 minutes.

  5. 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).

  6. Lint + compile regression. forge build (or solc on modified contracts) to confirm no compilation regression; forge fmt --check for style.

  7. Final test run. forge test to confirm the suite passes; record any new failure.

Show full SKILL.md (224 more words)Show less

When to pivot

  • Slither false-positive flood: narrow with --detect <high-signal list> and add a .slither.config.json suppression for known project FPs.
  • myth times 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 myth evidence.
  • Do NOT run Echidna/Medusa without invariant tests — property-less fuzzing yields nothing.
  • Do NOT run myth on 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.

Example

bash
# Step 1: static analysis (native)
slither . --exclude naming-convention,solc-version

# 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 test

Recording (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.

© mtarcure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/evm-audit-flow of mtarcure/claude-vibe-squad.

Open the folder on GitHubat commit 7bd69f8

Compare with similar skills

Evm Audit Flow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Evm Audit Flow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Evm Audit Flow this skillmtarcure/claude-vibe-squad164—~1.5kAutomated safety check: PassMIT
Audit Prep Assistanttrailofbits/skills7.4k—~2.5kAutomated safety check: PassCC-BY-SA-4.0
Slither Analysisccashwell/evm-cortex131—~1.5kAutomated safety check: PassMIT
Semgrep Triagedeonmenezes/mantishack504—~312Automated safety check: PassApache-2.0
Audit PrepPlamenTSV/plamen303—~3.7kAutomated safety check: PassMIT
Flounderadshao/flounder519—~9.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Audit Prep Assistant

    trailofbits/skills

    Official

    Gets your own codebase ready for an external security review: sets review goals, runs static analysis, raises test coverage, removes dead code and writes documentation.

    7.4k GitHub stars~2.5k tokensUpdated 2 days ago
    SecurityAuto-check passed

  • Slither Analysis

    ccashwell/evm-cortex

    A skill your agent uses when running Slither static analysis on Solidity contracts.

    131 GitHub stars~1.5k tokensUpdated 10 days ago
    Backend & APIsAuto-check passed

  • Semgrep Triage

    deonmenezes/mantishack

    Run semgrep via the mantissemgrep MCP server and triage results into the candidate/confirmed/rejected lifecycle

    504 GitHub stars~312 tokensUpdated 6 days ago
    SecurityAuto-check passed

  • Audit Prep

    PlamenTSV/plamen

    Prepare Solidity projects for a security audit — test coverage, test quality, NatSpec docs, code hygiene, dependency health, best-practice enforcement, deployment readiness, and project…

    303 GitHub stars~3.7k tokensUpdated 13 days ago
    SecurityAuto-check passed

  • Flounder

    adshao/flounder

    Operates Flounder, an autonomous white-hat security auditor.

    519 GitHub stars~9.2k tokensUpdated 4 days ago
    SecurityAuto-check passed

  • Ethereum Smart Contract Vulnerability Analysis

    tradecatlabs/vibe-coding-cn

    Runs Slither and Mythril against Solidity contracts to find reentrancy, overflow and access-control bugs before mainnet deployment, then triages and reports findings.

    17k GitHub starsUsed in 1 repo~738 tokens
    SecurityAuto-check passed

More from mtarcure/claude-vibe-squad

All 17 skills in this repo

  • Systematic Attacking

    mtarcure/claude-vibe-squad

    A skill your agent uses for ALL authorized offensive-security / bug-bounty work — the single method to find, chain, prove, dedup, and package the highest-value (High/Critical) findings across every…

    164 GitHub stars~3.6k tokensUpdated 19 days ago
    Auto-check passed

  • Blind Rediscovery

    mtarcure/claude-vibe-squad

    Operational checklist + helper for blind-rediscovery fan-out work.

    164 GitHub stars~1.6k tokensUpdated 19 days ago
    Auto-check passed

  • Chain Construct Smart Contract

    mtarcure/claude-vibe-squad

    A skill your agent uses when you have a confirmed on-chain vulnerability hypothesis and must demonstrate it with a passing proof-of-concept — author an attacker contract or crafted instruction…

    164 GitHub stars~1.5k tokensUpdated 19 days ago
    Auto-check passed

  • Compact Now

    mtarcure/claude-vibe-squad

    Operator-triggered proactive compaction — Chrono externalizes load-bearing state (active decisions, open tasks, next action) to a snapshot + a durable Vault learning note before invoking Claude…

    164 GitHub stars~1.6k tokensUpdated 19 days ago
    Auto-check passed

  • Agent Prompt Engineering

    mtarcure/claude-vibe-squad

    A skill your agent uses when building or revising the system prompt for a product agent and you need an eval-backed boundary, tool-use, grounding, and output contract.

    164 GitHub stars~872 tokensUpdated 19 days ago
    Auto-check: warnings

  • Defi Invariant Check

    mtarcure/claude-vibe-squad

    A skill your agent uses when the audit target is a DeFi protocol — AMM, lending market, yield vault, stablecoin, or perps — and you must author the economic properties generic campaigns miss, such…

    164 GitHub stars~2.5k tokensUpdated 19 days ago
    Auto-check passed

Works with

Categories

Questions about Evm Audit Flow

What does Evm Audit Flow do?

A skill your agent uses 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…. Evm Audit Flow is an agent skill from mtarcure/claude-vibe-squad. 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.

When should I use Evm Audit Flow?

Evm Audit Flow fits situations like: you have a Foundry; hardhat repository of Solidity; vyper contracts and want the end-to-end EVM review workflow on native CLIs — a slither static pass; semgrep taint rules.

How do I install Evm Audit Flow in Claude Code?

Run `npx skills add mtarcure/claude-vibe-squad --skill evm-audit-flow -a claude-code`. Or copy the skill folder (.agents/skills/evm-audit-flow in mtarcure/claude-vibe-squad) into .claude/skills/evm-audit-flow in your project. Claude Code loads it when a task matches its description.

How do I install Evm Audit Flow in Codex?

Run `npx skills add mtarcure/claude-vibe-squad --skill evm-audit-flow -a codex`. Or copy the skill folder (.agents/skills/evm-audit-flow in mtarcure/claude-vibe-squad) into .agents/skills/evm-audit-flow in your project. Codex loads it when a task matches its description.

Can I use Evm Audit Flow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mtarcure/claude-vibe-squad --skill evm-audit-flow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/evm-audit-flow, .gemini/skills/evm-audit-flow, .github/skills/evm-audit-flow and .opencode/skills/evm-audit-flow in your project.

What does Evm Audit Flow need to run?

SKILL.md names no scripts, command-line tools or credentials: Evm Audit Flow is instructions for the agent only.

Does Evm Audit Flow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Evm Audit Flow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Evm Audit Flow use?

Evm Audit Flow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Evm Audit Flow use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Evm Audit Flow?

Skills that share tags, products or a category with Evm Audit Flow: Audit Prep Assistant (trailofbits/skills, 7.4k stars), Slither Analysis (ccashwell/evm-cortex, 131 stars), Semgrep Triage (deonmenezes/mantishack, 504 stars) and Audit Prep (PlamenTSV/plamen, 303 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Evm Audit Flow?

mtarcure (a GitHub user) maintains it in mtarcure/claude-vibe-squad, which has 164 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 21, 2026.

Source: mtarcure/claude-vibe-squad on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.