verify

# Adversarial Verification Three agents with competing incentives: one finds issues, one disproves them, one judges. ## Standalone Codex Skip the Claude marker below. Create each fresh panelist with `spawn_agent`, deliver context while it runs with `send_message`, trigger another turn once it is idle with `followup_task`, wait with `wait_agent`, and stop its current turn with `interrupt_agent` only when necessary. Never spawn `codex-verifier` and never run `codex-run.ts` from inside Codex. Only read-only reviewers may overlap. Writers share the working tree unless the live host explicitly offers isolation, so any implementer and test-writer follow-up must use non-overlapping ownership and run serially. **Claude-only marker:** standalone Codex must skip this command. `mkdir -p ~/.claude/tmp && echo "verify" > ~/.claude/tmp/heavy-skill-active && date -u +"%Y-%m-%dT%H:%M:%SZ" >> ~/.claude/tmp/heavy-skill-active` ## When to Use - Security-sensitive code (auth, crypto, permissions) - Data integrity (migrations, schema changes, ETL) - Financial logic (payments, billing, calculations) - Breaking changes (API contracts, public interfaces) ## The Three-Agent Pattern ### Agent 1: Finder ``` Agent(reviewer, "You are a bug finder. Analyze the following code/changes thoroughly. Score yourself: +1 for low-impact issues, +5 for medium-impact, +10 for critical. Report every potential issue you find — edge cases, race conditions, missing validation, security holes, logic errors, per...