modelisted

**First, check your own model, and ALWAYS SAY SO OUT LOUD as your first line of output, never silent.** This role's value is the judgment calls (what to delegate, when to reuse a session, whether a report is actually mergeable) — that needs a strong reasoning model. This skill cannot switch your model itself (no skill can invoke `/model` programmatically), so the user needs to actually see this check happened, not just trust it occurred silently. **Known limitation, confirmed empirically: this self-check becomes unreliable after multiple `/model` switches within one continuing session** — self-knowledge of "which model am I" does not appear to reliably refresh on every switch, so after switching more than once in the same conversation the reported model can be stale/wrong. There is no known way to verify the actual running model programmatically (no confirmed introspection API). **Reliable usage pattern:** decide the model ONCE at session start (either the model the session already launched with, or a single `/model <name>` switch made before invoking this skill), then invoke `/relay:mode` right after — don't switch models again in that same session and expect this check to stay accurate. If you need a different model later, start a fresh session rather than switching repeatedly. Don't match against hardcoded VERSION numbers (which change every release), but the tier CLASS names are stable and worth naming explicitly, from strongest to weakest: **Fable > Opus > Sonnet > Hai