Security Audit

Audit reports overwhelm with 100 agents producing excessive output

Use scope filters: /security-audit security for focused analysis. Request executive summary only. Filter by priority: Critical and High issues first.

Free tier resource optimization recommendations not specific enough

Specify service explicitly: 'Optimize Upstash Redis within free tier limits'. Request concrete configuration changes. Include current usage metrics for context.

Audit misses project-specific security risks in public repository

Provide threat context: 'Public repo with API keys in .env.example'. Specify deployment: Vercel Edge Functions. Request supply chain analysis explicitly.

CVSS scoring inconsistent with project's actual threat model

Provide deployment context: 'Internal tool vs public SaaS'. Adjust scoring with --threat-model=public-repo. Request contextualized risk assessment per environment.

Audit completion time exceeds token limits for large codebases

Run incremental audits by scope: security first, then performance. Use --quick for overview. Process high-risk areas separately: /security-audit src/auth.

Security audit fails to complete or crashes during execution

Check system resources (memory, disk space) are sufficient. Review audit configuration for errors. Run audit on smaller scope first. Check audit tool logs for specific errors.

Audit report is incomplete or missing critical sections

Verify all required audit checks are enabled. Review audit configuration completeness. Run audit with --comprehensive flag. Check for permission issues preventing full scan.

Audit findings are difficult to prioritize or act upon

Use --severity flag to filter by risk level. Review audit report with --prioritize flag. Group findings by category. Create action plan from high-severity findings first.