code-audit-finding
GitHub为DeepAudit的Finding代理提供源码审计支持,聚焦授权、逻辑缺陷等风险。强制遵循证据驱动原则,按固定顺序及项目特征加载参考文件,严格区分案例与代码证据,确保审计结论准确可靠。
Trigger Scenarios
Install
npx skills add larlarua/AutoCVE --skill code-audit-finding -g -y
SKILL.md
Frontmatter
{
"name": "code-audit-finding",
"tags": [
"finding",
"code-audit",
"source-audit",
"auth",
"idor",
"business-logic"
],
"description": "DeepAudit Finding overlay for source-code auditing with code-audit-main references, mandatory reading routes, and progressive WooYun disclosure."
}
Code Audit Finding Overlay
This skill adapts the code-audit-main knowledge base for DeepAudit's Finding agent.
Use this skill to strengthen source-code auditing for:
- authorization and access-control flaws
- IDOR and tenant-isolation issues
- business-logic and state-machine flaws
- file operations and path handling
- input-validation gaps
- attack-chain driven source-to-sink review
This skill keeps DeepAudit's current role split intact:
reconprovides project navigation and scopefindingproduces source-audit conclusionsverificationperforms follow-up validation
Required Startup Protocol
- Read this
SKILL.mdfirst withload_skill_body. - Use
skill_resource_lookup(mode="list")before opening a new reference directory family. - Use
skill_resource_lookup(mode="read")for every required file you rely on. - Do not claim a checklist, framework rule, control requirement, or case pattern unless you have actually read the corresponding file.
Fixed-First Reading Order
After reading this SKILL.md, always read these files first:
references/core/anti_hallucination.mdreferences/core/false_positive_filter.mdreferences/checklists/coverage_matrix.mdreferences/core/comprehensive_audit_methodology.mdreferences/core/data_flow_methodology.mdreferences/core/taint_analysis.md
Conditional Mandatory Reading
After the fixed-first set, route by project signals:
- Languages:
references/checklists/<language>.mdreferences/languages/<language>.md
- Frameworks:
references/frameworks/<framework>.md
- Security domains:
references/security/authentication_authorization.mdreferences/security/business_logic.mdreferences/security/file_operations.mdreferences/security/input_validation.mdreferences/security/api_security.mdreferences/security/race_conditions.md- plus other matching files under
references/security/
- Control verification:
references/adapters/<language>.yaml
Finding-Specific Constraints
- Audit must stay evidence-driven.
- Cases and historical vulns can guide search direction, but they never count as evidence.
- If you have not read the relevant reference file, do not say that topic is fully audited.
- If you want to claim a missing control at high confidence, read the matching adapter first.
- Use the references to guide code reading, not to replace code reading.
Progressive Disclosure for WooYun and Cases
Use four levels of disclosure:
- Default:
- do not preload WooYun case bodies
- Index first:
- read
references/wooyun/INDEX.md
- read
- Evidence-gated expansion:
- only after you already have project-specific code evidence may you read one or two related case files
- Strict evidence boundary:
- WooYun and real-world cases only expand search directions, bypass ideas, and missed-check hints
- they do not justify a finding on their own
Relevant case sources:
references/wooyun/references/cases/real_world_vulns.md
Intentionally Excluded From Required Runtime Flow
agent.md is preserved in this skill root for reference, but its deep multi-agent orchestration is not part of Finding's required runtime reading path.
The original upstream SKILL.md is preserved at:
references/core/original_skill_reference.md
Version History
- 97ce141 Current 2026-07-05 09:22


