setup-ramstacklisted

# Setup ramstack Write your host's section of `~/.agents/ramstack-models.md`, a config file that sets ramstack's model per role. The skills read it at run time and fall back to their inline defaults when a section or line is absent, so this is an override layer, not a requirement. The file is shared across hosts on purpose. Model slugs differ per host (`sonnet` means something in Claude Code and nothing in Codex or pi), so the file holds one `## <host>` section per tool, and every skill reads only the section for the host it is running in. Someone who switches between Claude Code, Codex, and pi runs this skill once in each and the tools stop stepping on each other. ## Steps ### 1. Identify the host and detect available models Identify which host you are running in from your own environment (your system prompt names it). Section labels: `claude-code`, `codex`, `pi`; for any other host, a short kebab-case name of the tool. Then enumerate the model slugs you can pass to a subagent in this session; that is the dependable source. - **Claude Code**: the `model` values the Agent tool accepts (typically `fable`, `opus`, `sonnet`, `haiku`). - **Codex**: the models the CLI exposes. - **pi**: the models the user has actually set up, not pi's full catalog. Enumerate authenticated providers and their models from pi's config (`~/.pi/agent/`, including `models.json` and custom entries) or the `/model` picker. The set is whatever the user configured, so always show what you found and