Codex Security Review
Use this skill when:
- auditing recent code changes
- reviewing for auth, data exposure, business-logic abuse, and app-layer risk
- feeding findings into monitor and heal
Goal
Produce high-signal findings with low false-positive noise.
Review priorities
- Auth bypass and privilege mistakes
- Data exposure and IDOR-style access issues
- Broken multi-tenant boundaries
- Unsafe input handling and injection surfaces
- Secrets/config mistakes
- Security regressions introduced by recent features
Method
- Review recent relevant changes.
- Read the implementation, not just the diff headline.
- Check business logic abuse paths, not only syntax-level issues.
- Confirm exploitability where possible using available runtime/data sources.
- Write findings by severity with exact affected area.
Severity guidance
Critical:
- direct unauthorized access to sensitive data
- privilege escalation
- production secret exposure
High:
- realistic auth or workflow bypass
- missing tenant isolation
- unsafe sensitive mutation path
Medium:
- defense-in-depth gap
- missing headers or weaker validation without clear exploit path
Output contract
Each finding should state:
- what is wrong
- why it matters in business terms
- where it lives
- what kind of fix is appropriate
- whether heal should attempt it automatically
Integration
- Feed actionable findings into Linear through monitor
- Only hand off to heal when the scope is bounded and verifiable