agent-sessionslisted

# Agent Sessions Delegate work to other agents, each in its own tmux session, without losing track of what they are doing. The naive version of this is `claude --dangerously-skip-permissions "..."` as a bare subprocess. That works right up until you want two of them at once, or you need to know whether one finished, or one corrupts a working tree the other is editing, or a runaway spawns more of itself. This skill is the same idea with those failure modes engineered out. Use `scripts/agent-session`. Add it to PATH or call it by absolute path. ## When delegation is worth it Spawning a child costs real tokens and real wall-clock. It pays off when: - **Work is genuinely parallel.** Three independent audits of three subsystems finish in the time of the slowest, not the sum. - **You want an independent judgement.** A child that has never seen your reasoning is a far better reviewer than you reviewing yourself. Cross-engine is stronger still: Codex has not read your context window. - **The task is long and you want to stay responsive.** Detach, keep working, collect later. - **The work is risky to your own tree.** A child in its own git worktree can fail without touching what you have. It is not worth it for something you could do in two tool calls. A child pays a fixed startup cost and cannot see your context, so anything you delegate has to be described from scratch. ## Pick a model tier deliberately **Default to `--tier cheap`.** The single biggest waste in mu