grok-model-retirement-checklisted

# Skill: Grok Model Retirement Check Grok model retirements can redirect API calls silently to a higher-priced model without surfacing an error. A developer calling a retired model ID may be charged at the current model's rate without realizing it. This skill identifies retired IDs, confirms the redirect target, and flags billing consequences before they compound. ## When to reach for this skill - A developer mentions any Grok model ID — run the check first, answer the question second. - A developer reports unexpected Grok billing charges. - The agent is about to recommend any Grok model — verify it is not retired. - A developer is migrating from one Grok model to another. ## Step 1 — Identify the model ID in use Capture the exact model ID string the developer is using (e.g., from their API call, config file, or `.env`). Do not assume the model name is the same as the current lineup name — Grok model IDs and display names differ, and deprecated IDs may still accept calls. ## Step 2 — Check the retirement list Consult [`../../knowledge/cross-tool-model-lineup-2026.md`](../../knowledge/cross-tool-model-lineup-2026.md) Grok section — specifically the retirement/redirect table. Flag the following scenarios: | Scenario | Risk | Action | |---|---|---| | ID is in the active lineup | None currently | Confirm availability and pricing marker | | ID is in the retirement list with a known redirect | Billing: charged at redirect-target pricing | Flag the redirect; recommend explic