Update every repo from one catalog

Add this to AGENTS.md

## Model updates

Fetch https://aistackregistry.com/index.json once before checking my repos. Reuse that catalog for every repo in this update. Compare each repo's model IDs, limits, and provider settings. Tell me what should change before editing. After I approve, make the changes and run each repo's existing checks. If the catalog is missing a fact you need, tell me instead of guessing.

Then tell Codex which model you want and which repositories to check.

Add this to CLAUDE.md

## Model updates

Fetch https://aistackregistry.com/index.json once before checking my repos. Reuse that catalog for every repo in this update. Compare each repo's model IDs, limits, and provider settings. Tell me what should change before editing. After I approve, make the changes and run each repo's existing checks. If the catalog is missing a fact you need, tell me instead of guessing.

Then tell Claude Code which model you want and which repositories to check.

Install the shared model-update skill

Codex and Claude Code use the same SKILL.md. It reads repository instructions and model configuration, fetches the catalog once, and reuses the same bytes for every repo. It makes requested changes when the catalog supports them, skips unknown or blocked repos, and reports what changed or was skipped.

Install for Codex

skill_dir="${CODEX_HOME:-$HOME/.codex}/skills/update-ai-models"
mkdir -p "$skill_dir"
curl --fail --silent --show-error \
  https://aistackregistry.com/skill/SKILL.md \
  --output "$skill_dir/SKILL.md"

Restart Codex, then ask it to use the update-ai-models skill for the repositories you name.

Install in a Claude Code project

mkdir -p .claude/skills/update-ai-models
curl --fail --silent --show-error \
  https://aistackregistry.com/skill/SKILL.md \
  --output .claude/skills/update-ai-models/SKILL.md

Restart Claude Code in the project, then ask it to use the update-ai-models skill.

Check pinned model facts in CI

CI can fetch the catalog once and compare a model ID, token limit, or provider setting your app pins. It will not choose an upgrade for you.

Check that a configured model ID exists

This example assumes config/ai.json contains a model field. Change the file and field to match your repo. The job reads files. It does not update them or call a provider.

- name: Check configured AI model
  shell: bash
  env:
    MODEL_CONFIG: config/ai.json
  run: |
    set -euo pipefail
    catalog="$RUNNER_TEMP/aistackregistry-index.json"
    curl --fail --silent --show-error \
      https://aistackregistry.com/index.json \
      --output "$catalog"
    model_id="$(jq -r '.model' "$MODEL_CONFIG")"
    if ! jq -e --arg id "$model_id" \
      '.models | any(.api_model_id == $id or .registry_id == $id)' \
      "$catalog" >/dev/null
    then
      echo "::error::Configured model is missing from AI Stack Registry: $model_id"
      exit 1
    fi

This check catches an unknown model ID. Add explicit comparisons for any limits or provider settings your app pins. Ask Codex or Claude Code to review new model releases when you want to choose an upgrade.