List every model usable by each installed AI CLI (claude, codex, copilot, antigravity, kiro) and attach capability tags from references/model-tags.md. Also resolves each SDLC stage's designated model chain via tools/model-config.sh (project .jsc/models overrides $JSC_HOME/models.conf) and states which tags each phase requires, so jsc-sdlc skills gate on the designated model first and fall back to capability tags. Use when checking model fitness, inventorying models, or reviewing designated-model routing; not for switching models or editing the config files.
models — list CLI models with capability tags
Steps
Run jsc-cli/tools/detect-clis.sh to get the installed CLIs.
For each CLI, read the available models and the model currently in use. This step MUST run as a sub agent:
CLI
Source
claude
model in ~/.claude/settings.json; known families are in the claude rows of model-tags.md
codex
model in ~/.codex/config.toml
copilot
model options listed in the copilot config (~/.config/copilot/)
antigravity
models listed in the agy config
kiro
models listed in the kiro config
If a config is unreadable, list that CLI's known default models and mark each one with the literal label 「預設推定」 (assumed default).
3. Attach capability tags to every model per references/model-tags.md. Handle unlisted models per the closing rule of that file.
4. Output a table with four columns: CLI, model, tags, currently in use.
5. Append the SDLC phase requirement table (plan and analyze need reasoning-high; implement needs coding; maintain accepts any), so jsc-sdlc skills can gate on model capability.
6. Run jsc-cli/tools/model-config.sh list and append a 「階段指定模型」 table right after the phase requirement table, with three columns: stage, designated chain, source (project / global). State below the table that jsc-sdlc gates resolve the designated model first and fall back to capability tags only when a stage has no designated model. Done when the table shows all four stages, with - for unconfigured ones.