audit-breadth-scan

Name: audit-breadth-scan
Availability: InStock
Author: ccashwell

Map attack surfaces and prioritize high-risk functions across contracts during audits.

120|12|Updated Apr 10, 2026

Search Tags:#security #audit #risk-assessment #contracts #attack-surface #breadth-scan

Ready to run

npx skills add https://github.com/ccashwell/evm-cortex --skill audit-breadth-scan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-breadth-scan
Source: https://github.com/ccashwell/evm-cortex/tree/main/skills/audit-breadth-scan
Command: npx skills add https://github.com/ccashwell/evm-cortex --skill audit-breadth-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic breadth-first review of all contracts during security audits is essential to ensure no function, interface, or contract escapes initial risk assessment.

Core Features & Use Cases

Contract-level assessment: quickly evaluate each contract for surface exposure, dependencies, and upgrade risks.
Function-level risk mapping: identify high-risk functions and pathways across the codebase.
Attack surface mapping: enumerate entry points and potential abuse vectors to guide depth analysis.
Depth-analysis leads: generate prioritized leads (P0-P3) for targeted deep dives.

Quick Start

Initiate a breadth-scan across all contracts in scope to identify high-risk areas and leads for depth analysis.

Frequently Asked Questions about audit-breadth-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a breadth scan for smart contract security audits?▼

A breadth scan systematically maps security risk across all contracts by evaluating surface exposure, dependencies, and upgrade risks to ensure no function escapes initial risk assessment.

How do I map the attack surface across multiple smart contracts?▼

To map the attack surface across multiple contracts, perform a contract-level assessment to enumerate entry points and potential abuse vectors, then use a function risk matrix to identify high-risk pathways.

How do I identify high-risk functions for depth analysis during a contract audit?▼

Identify high-risk functions for depth analysis by generating prioritized leads from P0 to P3 during the attack surface mapping phase, establishing clear transition criteria for targeted deep dives.

Can I use a breadth scan for contract-level risk assessment before depth analysis?▼

Yes, a breadth scan is applicable for contract-level assessments to quickly evaluate surface exposure and dependencies, producing clear transition criteria to guide subsequent depth-analysis leads.

What is the best way to prioritize security audit leads across a codebase?▼

Prioritize audit leads by executing a pass-based methodology that ranks functions from P0 to P3 based on risk severity, ensuring depth analysis targets the most critical attack surface vectors first.

When should I not use a breadth scan for contract security audits?▼

Avoid using a breadth scan when you need to investigate a specific, known vulnerability in depth, as this methodology focuses on breadth-first risk assessment rather than isolated depth-analysis execution.