Methodology Skill
Purpose
Comprehensive audit methodology guides covering the full security auditor workflow — from preparation and AI-assisted analysis through formal verification, economic modeling, and report writing.
Core Methodologies
Audit Workflow
- LLM Audit Workflow - Structured AI playbook with phases, modes, and context transfer
- AI-Assisted Auditing - Prompt engineering, automation scripts, and tool comparison
- Prompt Evolution - Beam search optimization system for audit prompts
Testing & Verification
- Invariant Testing - Foundry stateful fuzzing with handler patterns and ghost variables
- Symbolic Execution - Halmos, HEVM, and Certora formal verification
- PoC Writing Guide - Proof of concept templates for all major vulnerability types
Attack Analysis
- Economic Attack Modeling - Flash loan profitability, game theory, tokenomics analysis
- Composability Attacks - Cross-protocol attack patterns (oracle, liquidity, donation)
- Exploit Case Studies - Forensic analysis of $100M+ historical hacks
- Learning Path & Attack Vectors - Structured learning path with top 10 attack patterns
Security Patterns
- Secure Pattern Reference - Quick-reference for correct implementations (CEI, oracles, vaults)
- Gas Optimization Security - When gas optimization introduces vulnerabilities
- Fix Verification Patterns - Ensuring fixes don't introduce new bugs
Protocol-Specific
- Fork Audit - Diff-based methodology for auditing protocol forks
- Upgrade & Migration Patterns - Proxy, initialization, and storage layout security
Reporting
- Audit Report Templates - Finding format, severity matrix, PoC templates, executive summary
Skill Quality & Authoring
- Quality Scoring - 10-point Anthropic best practices scoring framework for evaluating skill quality
- Skill TDD Methodology - Test-Driven Documentation: pressure test → baseline → write → verify → close loopholes
- Skill Authoring Guide - Three creation paths, progressive disclosure, quality guarantee loop, version tracking
Usage
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
Related Skills
Prerequisites
Methodology skills require familiarity with at least one blockchain platform. Formal verification methods (Halmos, Certora) require their respective tool installations.
Validation
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
Behavior Guidelines
- LLM Audit Workflow MUST be the starting point for all AI-assisted audits
- Invariant testing is required for DeFi protocol audits
- Symbolic execution may optionally be applied when formal guarantees are needed
- PoC writing is ALWAYS expected for HIGH and CRITICAL severity findings
References
- Methodology References - Workflow comparison charts and tool integration guides
1---2name: methodology3description: 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.4---56# Methodology Skill78## Purpose9Comprehensive audit methodology guides covering the full security auditor workflow — from preparation and AI-assisted analysis through formal verification, economic modeling, and report writing.1011## Core Methodologies1213### Audit Workflow14- [LLM Audit Workflow](llm-audit-workflow.md) - Structured AI playbook with phases, modes, and context transfer15- [AI-Assisted Auditing](ai-assisted-auditing.md) - Prompt engineering, automation scripts, and tool comparison16- [Prompt Evolution](prompt-evolution.md) - Beam search optimization system for audit prompts1718### Testing & Verification19- [Invariant Testing](invariant-testing.md) - Foundry stateful fuzzing with handler patterns and ghost variables20- [Symbolic Execution](symbolic-execution.md) - Halmos, HEVM, and Certora formal verification21- [PoC Writing Guide](poc-writing-guide.md) - Proof of concept templates for all major vulnerability types2223### Attack Analysis24- [Economic Attack Modeling](economic-attack-modeling.md) - Flash loan profitability, game theory, tokenomics analysis25- [Composability Attacks](composability-attacks.md) - Cross-protocol attack patterns (oracle, liquidity, donation)26- [Exploit Case Studies](exploit-case-studies.md) - Forensic analysis of $100M+ historical hacks27- [Learning Path & Attack Vectors](learning-path-attack-vectors.md) - Structured learning path with top 10 attack patterns2829### Security Patterns30- [Secure Pattern Reference](secure-pattern-reference.md) - Quick-reference for correct implementations (CEI, oracles, vaults)31- [Gas Optimization Security](gas-optimization-security.md) - When gas optimization introduces vulnerabilities32- [Fix Verification Patterns](fix-verification-patterns.md) - Ensuring fixes don't introduce new bugs3334### Protocol-Specific35- [Fork Audit](fork-audit.md) - Diff-based methodology for auditing protocol forks36- [Upgrade & Migration Patterns](upgrade-migration-patterns.md) - Proxy, initialization, and storage layout security3738### Reporting39- [Audit Report Templates](audit-report-templates.md) - Finding format, severity matrix, PoC templates, executive summary4041### Skill Quality & Authoring42- [Quality Scoring](quality-scoring.md) - 10-point Anthropic best practices scoring framework for evaluating skill quality43- [Skill TDD Methodology](skill-tdd.md) - Test-Driven Documentation: pressure test → baseline → write → verify → close loopholes44- [Skill Authoring Guide](skill-authoring-guide.md) - Three creation paths, progressive disclosure, quality guarantee loop, version tracking4546## Usage47```481. Start with LLM Audit Workflow for structured phase-by-phase approach492. Apply protocol-specific methodology (fork-audit, economic-modeling, etc.)503. Use testing tools (invariant testing, symbolic execution) for verification514. Write PoCs following poc-writing-guide525. Generate report using audit-report-templates53```5455## Related Skills56- [Checklists](../checklists/index.md) - Protocol-specific audit checklists57- [Patterns](../patterns/) - Vulnerability pattern library58- [Exploit Forensics](../exploit-forensics/) - Historical exploit deep dives59- [Severity](../severity/) - Finding severity classification6061## Prerequisites6263Methodology skills require familiarity with at least one blockchain platform. Formal verification methods (Halmos, Certora) require their respective tool installations.6465## Validation6667To verify methodology completeness, validate all referenced files exist:6869```bash70# Verify all methodology files are present71for f in llm-audit-workflow.md invariant-testing.md symbolic-execution.md poc-writing-guide.md; do72 test -f "$f" && echo "OK: $f" || echo "MISSING: $f"73done74```7576```python77# Test methodology coverage78def validate_methodology_files():79 required = ['llm-audit-workflow.md', 'invariant-testing.md', 'poc-writing-guide.md']80 for f in required:81 assert os.path.exists(f), f"Missing methodology file: {f}"82 print("All methodology files verified")83```8485```yaml86# Methodology selection guide87audit_type: full88required_methods:89 - llm-audit-workflow # ALWAYS required90 - invariant-testing # Required for DeFi91optional_methods:92 - symbolic-execution # For formal verification93 - economic-modeling # For tokenomics review94```9596## Behavior Guidelines9798- LLM Audit Workflow MUST be the starting point for all AI-assisted audits99- Invariant testing is **required** for DeFi protocol audits100- Symbolic execution may optionally be applied when formal guarantees are needed101- PoC writing is ALWAYS expected for HIGH and CRITICAL severity findings102103## References104105- [Methodology References](references/README.md) - Workflow comparison charts and tool integration guides