skills/methodology/SKILL.md
Comprehensive audit methodology guides covering the full security auditor workflow -- from preparation and AI-assisted analysis through formal verification, economic modeling, report writing, and skill quality scoring. Use when learning audit workflows, selecting testing strategies, or authoring new skills with TDD methodology.
npx skillsauth add 0x-shashi/web3-audit-skills skills/methodologyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive audit methodology guides covering the full security auditor workflow — from preparation and AI-assisted analysis through formal verification, economic modeling, and report writing.
1. Start with LLM Audit Workflow for structured phase-by-phase approach
2. Apply protocol-specific methodology (fork-audit, economic-modeling, etc.)
3. Use testing tools (invariant testing, symbolic execution) for verification
4. Write PoCs following poc-writing-guide
5. Generate report using audit-report-templates
Methodology skills require familiarity with at least one blockchain platform. Formal verification methods (Halmos, Certora) require their respective tool installations.
To verify methodology completeness, validate all referenced files exist:
# Verify all methodology files are present
for f in llm-audit-workflow.md invariant-testing.md symbolic-execution.md poc-writing-guide.md; do
test -f "$f" && echo "OK: $f" || echo "MISSING: $f"
done
# Test methodology coverage
def validate_methodology_files():
required = ['llm-audit-workflow.md', 'invariant-testing.md', 'poc-writing-guide.md']
for f in required:
assert os.path.exists(f), f"Missing methodology file: {f}"
print("All methodology files verified")
# Methodology selection guide
audit_type: full
required_methods:
- llm-audit-workflow # ALWAYS required
- invariant-testing # Required for DeFi
optional_methods:
- symbolic-execution # For formal verification
- economic-modeling # For tokenomics review
development
Systematically hunt for every variant of a discovered vulnerability across the entire codebase. Use when a bug is found and all instances of the same root cause pattern must be identified, or when performing variant analysis during competitive audits on Code4rena or Sherlock.
testing
Use when the user wants to audit TON smart contracts for security vulnerabilities, scan FunC or Tact contracts for message chain replay, bounce handling, or gas issues, review TON DeFi protocols for actor-model concurrency flaws, or analyze asynchronous message passing security.
tools
Analyze ERC20/ERC721/ERC1155 token implementations for non-standard behavior, fee-on-transfer mechanics, rebasing logic, blacklists, pausability, and integration risks. Use when reviewing protocols that interact with external tokens or implementing token-related features.
testing
Use when the user wants to audit Sui Move smart contracts, scan Sui-specific patterns including object ownership, shared objects, or dynamic fields, review Sui DeFi protocols for object model security issues, or analyze Sui-specific transaction and consensus patterns.