Setup pstack

Write ~/.config/pstack/pstack-models.md, the file that sets pstack's model per role. Skills read it when they spawn a worker.

Steps

1. Detect available models

Run ../rex-subagents/scripts/subagent models --probe-claude by absolute path, from this skill's directory (the one your harness gave when it loaded this file, else ~/.claude/skills/setup-pstack/ on Claude Code and ~/.agents/skills/setup-pstack/ on Codex). It lists what a worker can run, per harness. claude models are Claude Code's aliases for the latest model of each family, each probed with one tiny request, so keep only those with available: true. codex models come from Codex's own model cache, with the efforts each one lists, and default_model is the model in ~/.codex/config.toml. That is the only source. If a harness has no available model, say so and leave it out. An entry is claude/<model> or codex/<model>, plus (<effort>) from that model's efforts. Never write an entry it did not return. The aliases inherit-parent and auto are always valid even though they are not detected models.

2. Load current state

The default role-to-model mapping is the rule in step 3(b), over the roles shown in step 5. If ~/.config/pstack/pstack-models.md already exists, read it and treat its # budget line and its role values as the current choices. Otherwise start from those defaults. A line whose role is not in step 5, such as how critics, is from a retired role. Drop it.

3. Budget, map, and confirm

(a) Ask for a budget. Ask plainly in the chat. Offer these four options with these exact labels, and name the current budget when the file records one.