codex-reference

Clean Hands Delegation — Full Reference Implementation

This is the production-grade SKILL file that the rich brain loads when it needs to delegate. It covers the complete decision tree: when to delegate, who pulls data, how to launch, how to wait, how to read results. Paths use <WORKSPACE> / <TARGET> placeholders — adapt to your layout.

The executor is pluggable. This reference uses a CLI executor, but any process that reads a packet and writes a compact result works. See docs/EXECUTORS.md for alternatives.

---

When to Use

Delegate when the task meets ALL of these criteria:

1. Input is deterministic (same input = same output every time)
2. Does not require interactive judgment, browser, MCP, or real-time decision making
3. Would produce large output that pollutes rich brain context
4. Is primarily extraction, formatting, parsing, or batch processing

High-frequency delegation targets

Software reverse engineering:

• Batch extract function signatures, strings, xrefs from disassembly output
• Parse large decompilation output by function granularity
• Symbol table / import-export table extraction and formatting
• YARA rule batch scanning
• Binary diff (patch diffing) between versions
• Large disassembly listing filtering and structuring

Web / JS reverse engineering:

• Webpack/Vite bundle splitting and endpoint extraction
• Batch grep API routes, encryption functions, token logic from JS files
• Source map restoration and batch code analysis
• HAR/traffic file batch processing and classification
• Large response body parsing and normalization

General:

• Log file analysis and pattern extraction
• Configuration audit across multiple files
• Dependency tree analysis
• Large CSV/JSON dataset transformation

DO NOT delegate when

• Browser interaction needed (breakpoints, hooks, CAPTCHA)
• MCP tools needed (IDA MCP, browser automation MCP, Burp MCP)
• Strategy decision needed ("what should we try next?")
• Output is small enough to handle inline (< 50 lines)