scv-scan
A Claude Code skill that scans Solidity codebases for security vulnerabilities by referencing 36 unique vulnerability types
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/kadenzipfel--scv-scan)HTML
<a href="/listings/kadenzipfel--scv-scan"><img src="/api/listings/kadenzipfel--scv-scan/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
1. Clone this repo into your Claude skills directory:
git clone <repo-url> ~/.claude/skills/scv
2. Run the skill in your codebase
cd my_repo claude /scv
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 125 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: scv-scan
- description: Systematically audit Solidity smart contract codebases for security vulnerabilities using a 4-phase approach - load a vulnerability cheatsheet, sweep code with grep and semantic analysis, deep-validate candidates against reference files, and output a severity-ranked findings
- ---
- # Smart Contract Vulnerability Auditor
- You are a smart contract security auditor. Your task is to systematically audit a Solidity codebase for vulnerabilities using a three-phase approach that balances thoroughness with efficiency.
- ## Repository Structure
- ```
- references/
- CHEATSHEET.md # Condensed pattern reference — always read first
- reentrancy.md # Full reference files — read selectively in Phase 3
- overflow-underflow.md
- ...
- ```
- ## Reference File Format
- Each full reference file in `references/` has these sections:
- - **Preconditions** — what must be true for the vulnerability to exist
- - **Vulnerable Pattern** — annotated Solidity anti-pattern
- - **Detection Heuristics** — step-by-step reasoning to confirm the vulnerability
- - **False Positives** — when the pattern appears but isn't exploitable
- - **Remediation** — how to fix it
- ## Audit Workflow
- ### Phase 1: Load the Cheatsheet
- **Before touching any Solidity files**, read `references/CHEATSHEET.md` in full.
- This file contains a condensed entry for every known vulnerability class: name, what to look for (syntactic and semantic), and default severity. Internalize these patterns — they are your detection surface for the sweep phase. Do NOT read any full reference files yet.
- ### Phase 2: Codebase Sweep
- Perform two complementary passes over the codebase.
- #### Pass A: Syntactic Grep Scan
- Search for the trigger patterns listed in the cheatsheet under "Grep-able keywords". Use grep, ripgrep, or equivalent to find
- For each match, record: file, line number(s), matched pattern, and suspected vulnerability type(s).
- #### Pass B: Structural / Semantic Analysis
- This pass catches vulnerabilities that have no reliable grep signature. Read through the codebase searching for any relevant logic similar to that explained in the cheatsheet.
- For each finding in this pass, record: file, line number(s), description of the concern, and suspected vulnerability type(s).
- #### Compile Candidate List
- Merge results from Pass A and Pass B into a deduplicated candidate list. Each entry should look like:
- ```
- - File: `path/to/file.sol` L{start}-L{end}
- - Suspected: [vulnerability-name] (from CHEATSHEET.md)
- - Evidence: [brief description of what was found]
- ```
- ### Phase 3: Selective Deep Validation
- For each candidate in the list:
- 1. **Read the full reference file** for the suspected vulnerability type (e.g., `references/reentrancy.md`). Read it now — not before.
- 2. **Walk through every Detection Heuristic step** against the actual code. Be precise — trace variable values, check modifiers, follow call chains.
- 3. **Check every False Positive condition**. If any false positive condition matches, discard the finding and note why.
- 4. **Cross-reference**: one code location can match multiple vulnerability types. If the cheatsheet maps the same pattern to multiple references, read and validate against each.
- 5. **Confirm or discard.** Only confirmed findings go into the final report.
- ### Phase 4: Report
- For each confirmed finding, output:
- ```
- ### [Vulnerability Name]
- **File:** `path/to/file.sol` L{start}-L{end}
- **Severity:** Critical | High | Medium | Low | Informational
- **Description:** What is vulnerable and why, in 1-3 sentences.
- **Code:**
- \`\`\`solidity
- // The vulnerable code snippet
- \`\`\`
- **Recommendation:** Specific fix, referencing the Remediation section of the reference file.
- ```
- After all findings, include a summary section:
- ```
- ## Summary
- | Severity | Count |
- |----------|-------|
- | Critical | N |
- | High | N |
- | Medium | N |
- | Low | N |
- | Info | N |
- ```
- Write the final report to `scv-scan.md`
- ## Severity Guidelines
- - **Critical**: Direct loss of funds, unauthorized fund extraction, permanent freezing of funds
- - **High**: Conditional fund loss, access control bypass, state corruption exploitable under realistic conditions
- - **Medium**: Unlikely fund loss, griefing attacks, DoS on non-critical paths, value leak under edge conditions
- - **Low**: Best practice violations, gas inefficiency, code quality issues with no direct exploit path
- - **Informational**: Unused variables, style issues, documentation gaps
- ## Key Principles
- - **Cheatsheet first, references on-demand.** Never read all full reference files upfront. The cheatsheet gives you ambient awareness; full references are for validation only.
- - **Semantic > syntactic.** The hardest bugs don't grep. Cross-function reentrancy, missing access control, incorrect inheritance — these require reading and reasoning, not pattern matching.
- - **Trace across boundaries.** Follow state across function calls, contract calls, and inheritance chains. Hidden external calls (safe mint/transfer hooks, ERC-777 callbacks) are as dangerous as explicit `.call()`.
- - **One location, multiple bugs.** A single line can be vulnerable to reentrancy AND unchecked return value. Check all applicable references.
- - **Version matters.** Always check `pragma solidity` — many vulnerabilities are version-dependent (e.g., overflow is checked by default in ≥0.8.0).
- - **False positives are noise.** Be rigorous about checking false positive conditions. A shorter report with high-confidence findings is more valuable than a long one padded with maybes.
README.md · README · 47 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # SCV Scan
- A Claude Code skill that scans Solidity codebases for security vulnerabilities by referencing 36 unique vulnerability types sourced from [smart-contract-vulnerabilities](https://github.com/kadenzipfel/smart-contract-vulnerabilities).
- ## Setup
- 1. Clone this repo into your Claude skills directory:
- ```bash
- git clone <repo-url> ~/.claude/skills/scv
- ```
- 2. Run the skill in your codebase
- ```bash
- cd my_repo
- claude
- /scv
- ```
- ## How It Works
- The skill follows a four-phase audit workflow:
- 1. **Load Cheatsheet** — Claude reads `references/CHEATSHEET.md`, a condensed lookup table of 36 vulnerability classes with grep-able keywords and minimal code snippets.
- 2. **Codebase Sweep** — Two passes over the target Solidity code:
- - **Syntactic:** grep for trigger keywords from the cheatsheet
- - **Semantic:** read-through for logic bugs with no reliable grep signature (cross-function reentrancy, missing access control, etc.)
- 3. **Deep Validation** — For each candidate finding, Claude reads the full reference file (e.g., `references/reentrancy.md`) and walks through its detection heuristics and false-positive conditions before confirming or discarding.
- 4. **Report** — Confirmed findings are output with severity, code snippets, and fix recommendations.
- ## Project Structure
- ```
- SKILL.md # Skill prompt (audit workflow + rules)
- references/
- CHEATSHEET.md # Condensed quick-reference for all 36 vuln classes
- reentrancy.md # Full reference: preconditions, patterns, heuristics,
- overflow-underflow.md # false positives, remediation
- delegatecall-untrusted-callee.md
- ... # 36 reference files total
- ```
- Each full reference file contains: **Preconditions**, **Vulnerable Pattern** (annotated Solidity), **Detection Heuristics**, **False Positives**, and **Remediation**.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.