Menu
Use Codex CLI for sandboxed auditing, debugging, and autonomous prototyping
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Complex browser automation workflow using claude-in-chrome MCP with mandatory sequential-thinking planning. Use when automating multi-step web interactions, form filling, navigation sequences, or web scraping.
End-to-end testing workflow for validating complete user journeys through web applications using claude-in-chrome MCP. Specializes in test assertions, suite organization, evidence collection, and pass/fail reporting.
Screenshot-based visual comparison and regression testing using claude-in-chrome MCP. Captures, compares, and validates UI states to detect layout shifts, visual bugs, and design regressions across viewports.
Structured data extraction from web pages using claude-in-chrome MCP with sequential-thinking planning. Focus on READ operations, data transformation, and pagination handling for multi-page extraction.
Use when conducting comprehensive code review for pull requests across multiple quality dimensions. Orchestrates 12-15 specialized reviewer agents across 4 phases using star topology coordination. Covers automated checks, parallel specialized reviews (quality, security, performance, architecture, documentation), integration analysis, and final merge recommendation in a 4-hour workflow.
Create Claude Code hooks with proper schemas, RBAC integration, and performance requirements. Use when implementing PreToolUse, PostToolUse, SessionStart, or any of the 10 hook event types for automation, validation, or security enforcement.
| name | codex-audit |
| description | Use Codex CLI for sandboxed auditing, debugging, and autonomous prototyping |
| allowed-tools | Bash, Read, Write, TodoWrite, Glob, Grep |
Before writing ANY code, you MUST check:
.claude/library/catalog.json.claude/docs/inventories/LIBRARY-PATTERNS-GUIDE.mdD:\Projects\*| Match | Action |
|---|---|
| Library >90% | REUSE directly |
| Library 70-90% | ADAPT minimally |
| Pattern exists | FOLLOW pattern |
| In project | EXTRACT |
| No match | BUILD (add to library after) |
Route auditing and debugging tasks to Codex CLI when:
What Codex Does Better:
/codex-audit "Find and fix all type errors" --context src/
/codex-audit "Fix failing tests" --context tests/ --max-iterations 10
/codex-audit "Build REST API with CRUD endpoints" --context .
bash scripts/multi-model/codex-audit.sh "<task>" "<context>" "<task_id>" "<max_iterations>"
| Constraint | Value |
|---|---|
| Network | DISABLED |
| File Access | CWD only |
| Isolation | macOS Seatbelt / Docker |
| Max Iterations | 5 (configurable) |
Results stored to Memory-MCP:
multi-model/codex/audit/{task_id}{
"raw_output": "Audit findings...",
"metrics": {
"files_analyzed": 15,
"findings_count": 7,
"fixes_applied": 5
},
"context_path": "src/",
"sandbox_mode": true
}
After Codex audit completes:
// Claude agent reads Codex audit
const audit = memory_retrieve("multi-model/codex/audit/{task_id}");
if (audit.metrics.findings_count > 0) {
Task("Reviewer", `Review findings: ${audit.raw_output}`, "reviewer");
}
# Phase 1: Theater detection (Claude)
/theater-detection-audit
# Phase 2: Functionality audit (Codex)
/codex-audit "Verify all functions work" --context src/
# Phase 3: Style audit (Claude)
/style-audit