←Leaderboard/Security/skills
Last commit on October 5, 2026·Created on February 23, 2026

pashov/skills

“Automates the creation of stateful Solidity fuzz suites for smart contract security audits.”
Combined rank
#307
across all skills
In Security
#16
category rank
Stars
1.3k
+2.8% in last 7d
Forks
237
+2.6% in last 7d
Watchers
20
0.0% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

This skill helps security researchers and smart contract developers generate Echidna and Medusa-compatible fuzz suites from existing Foundry or Hardhat projects. It structures the necessary runtime files and metadata to facilitate invariant campaigns.

Complementary tools allow for the conversion of English-language properties into concrete Solidity assertions, streamlining the transition from high-level property definitions to executable test harnesses.

WHO IT'S FOR
Smart contract security auditors
perform automated security audits of Solidity code
Blockchain developers
generate fuzz suites for Foundry or Hardhat projects
QA / Test automation engineers
implement property-based testing for smart contracts
Smart contract engineers
synchronize fuzzing harnesses with source code changes
Repository contents

5 skill files

Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

I’m using

Install bundle and run X-Ray

Installs: Complete Pashov Audit Group Skills repository bundle; the documented prompt immediately runs the x-ray skill after installation. · Claude Code, Cursor, Codex, GitHub Copilot, Windsurf

Before you start
  • A Solidity project codebase; X-Ray looks for Solidity files or a Foundry/Hardhat configuration at the project root or one level below.
  • A Bash environment with the `mkdir` utility, required by X-Ray's mandatory enumeration step.

Platform: Claude Code, Cursor, Codex, GitHub Copilot, or Windsurf

Run from: The target Solidity project root/codebase

  1. In a supported AI agent session opened at the target codebase, enter this prompt exactly. This is an agent-session prompt, not a terminal command.

    Install latest https://github.com/pashov/skills/ and run x-ray on the codebase
x-ray/README.md ↗ · Checked Oct 18, 2026fizz/skills/fizz-convert/SKILL.md ↗ · Checked Oct 18, 2026fizz/skills/fizz-sync/SKILL.md ↗ · Checked Oct 18, 2026fizz/SKILL.md ↗ · Checked Oct 18, 2026x-ray/SKILL.md ↗ · Checked Oct 18, 2026README.md ↗ · Checked Oct 18, 2026solidity-auditor/SKILL.md ↗ · Checked Oct 18, 2026

Give it something to do.

Suggested first task

Generate a focused fuzzing suite

Uses fizz

  • A Foundry or Hardhat lending-protocol project opened as the working directory.
Using the fizz skill, generate a fuzz suite for this lending protocol. Focus on solvency and liquidation invariants.
fizz/references/setup-playbook.md ↗ · Checked Oct 18, 2026fizz/SKILL.md ↗ · Checked Oct 18, 2026fizz/README.md ↗ · Checked Oct 18, 2026
Suggested first task

Audit selected Solidity files

Uses solidity-auditor

  • Replace *specified files* with the paths of the Solidity files to audit; the author recommends targeting the 2–5 contracts currently being changed.
Run solidity-auditor on *specified files*.
solidity-auditor/README.md ↗ · Checked Oct 18, 2026solidity-auditor/SKILL.md ↗ · Checked Oct 18, 2026
Author’s example

Generate a pre-audit X-Ray

Uses x-ray

  • A Solidity protocol codebase opened as the working directory; if a path is supplied, X-Ray uses it as the project root.
run an x-ray on the codebase
x-ray/README.md ↗ · Checked Oct 18, 2026x-ray/SKILL.md ↗ · Checked Oct 18, 2026README.md ↗ · Checked Oct 18, 2026