security-audit

Codex compatibility note:

• Invoke $skill-name: load the registered .agents/skills/<name>/SKILL.md and execute it with Codex tools; no separate Skill tool or Claude mode switch is needed. Author .claude/**; mirrors are generated.
• Track steps before execution and keep progress/evidence current. Explicit skill requests execute their protocol. Use the native question tool for required questions.
• Map foreign tool names to available host capabilities. A name mismatch needs no approval; an actually unavailable required capability stops with its step/evidence and a user question before adaptation.
• Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
• Preserve protocol order unless the user approves a deviation. Workflows use $start-workflow: gates stay fixed; other steps may flex with logged reasons and evidence.

Quick Summary

Review modes: For review/audit work, standalone defaults to --review-only (--report-only alias); --fix-loop enables review → validate → authorized fix → fresh re-review, default cap 3. --fix-loop --loop-owner=caller returns a read-only pass to the caller that owns fixes/re-review. Create triage, review, validation and re-review todo tasks first; apply the carried review-policy contract for LOW deferral and user-approved bounded extensions. Non-review modes and terminal findings validation keep their own dispatch.

Goal: Review application, secrets, supply-chain, configuration, pipeline and host risks against OWASP Top 10 (2025) and D1–D10, so credible security failures are exposed and resolved with evidence before handoff.

Summary:

• Route: Scope (changes/full/deps/vet/host) → Audit selected D1–D10 domains → Report severity, confidence and remediation → Validate Findings with $why-review --validate-findings → approved Fix + Full Re-Review with a fresh security-auditor. Round 1 clears every severity; Round 2 clears CRITICAL/HIGH/MEDIUM and defers LOW; binary gates always block.
• Cover every selected surface, beyond application code. D2 secrets always runs; D4 vetting precedes the first third-party install/clone/run, including automation.
• Prove findings with file:line or exact command+output; trace exploitability or label "potential risk, not confirmed". Save findings to tmp/reports/security-audit-{YYMMDD}-{HHmm}-{slug}.md.
• --report-only: steps 1–4 only; no fix, restart, nested agents, user question or writer beyond the report. The caller owns fixes; see Report-Only Mode.

Use $security-audit; /security and /arch-security-review do not resolve.

[BLOCKING] Execute skill steps in declared order. NEVER skip, reorder, or merge steps without explicit user approval. Inside a workflow run, $start-workflow → Workflow-step mode bounds this rule. [BLOCKING] Before each step or sub-skill call, update todo tracking: set in_progress when step starts, set completed when step ends. [BLOCKING] Every completed/skipped step MUST include brief evidence or explicit skip reason. [BLOCKING] If Task tools are unavailable, create and maintain an equivalent step-by-step plan tracker with the same status transitions.

Workflow:

1. Scope — Resolve scope mode (changes/full/deps/vet/host) and select security domains
2. Audit — Review every selected domain checklist (D1–D10) with file:line / command-output evidence
3. Report — Document findings with severity, confidence, and remediation
4. Validate Findings — Run $why-review --validate-findings <report-path> before any fix
5. Fix + Full Re-Review — Fix only validated findings that block the current round, then restart full security review from Scope; Round 2 LOW-only findings end the loop without another cycle. Not run under --report-only.