modelisted

Triggered by /mode, /mode default, or /mode god-mode. Reads or switches the current project's model mode without re-running /init: writes .claude/model-mode.json, updates the model field in the project's .claude/settings.json (merge, never clobber), and — if /boiler has already added a "## Model Policy" section to CLAUDE.md — updates that section in place so the human-readable copy stays in sync.
orassayag/agentic-project-workflow · ★ 1 · AI & Automation · score 65

Install: claude install-skill orassayag/agentic-project-workflow

# mode Skill ## Commands - `/mode` — print the current mode and what each workflow step resolves to - `/mode default` — cap model usage at the ceiling tiers; never auto-invoke the top-tier model - `/mode god-mode` — allow the strongest model, but only for the steps flagged as escalating in `~/.claude/bank/model-tiers.md` Mode is per-project state in `.claude/model-mode.json` (missing file = `default`). The tier→model mapping and the per-step escalation table live in `~/.claude/bank/model-tiers.md` — that file is the single source of truth; never restate model ids in this skill. All steps use the shared helper: ```bash source ~/.claude/skills/_lib/model-tier.sh ``` --- ## `/mode` (no argument) — report only 1. `read_model_mode` — print the current mode. 2. Print the per-step resolution using `resolve_model <step>` for each step row in `~/.claude/bank/model-tiers.md`. 3. Stop. Change nothing. ## `/mode <default|god-mode>` — switch ### Step 1 — Validate the argument Anything other than `default` or `god-mode`: stop and tell the developer the two valid values. Do not guess at intent. ### Step 2 — Write the mode state ```bash write_model_mode "<mode>" "/mode <mode>" ``` ### Step 3 — Update the project default model ```bash apply_project_default_model ``` This merges the `model` field into `.claude/settings.json` — creating the file if absent, never clobbering unrelated keys — and prints the restart notice. The notice is informational, not a hard stop. ### Step 4