meta-security-review-bundle

Run the security review bundle over the candidate operation. It applies a policy gate that denies modifications to system paths like /etc/ or credential exfiltration, plus a secret scanner that flags API keys, tokens, and private keys, then arbitrates a final DENY, WARN, or ALLOW verdict.

The rule applies strict priority: a policy_review DENY always wins and its reason passes through verbatim; otherwise a secret_scan WARN requires explicit user acknowledgement; only when policy allows and the scan is clear does it return ALLOW.

The scanner detects API keys (sk-, ghp_, AKIA, AIza patterns), JWT and OAuth bearer tokens, PEM private keys, database connection URIs with embedded passwords, and plaintext passwords next to labels like pwd= or password:.

If a gate errors, times out, or returns an empty deliverable, the orchestrator's failure cascade produces a structured failure payload. Operators review the partial verdicts in step_outputs and decide manually rather than getting an automatic verdict.

Avoid it when only one rule set genuinely applies, because the combinator pattern multiplies token cost by the number of gates for a single turn. Prefer a single well-defined orchestrator sequence for routine reviews.