Fetch once
Codex or Claude Code downloads /index.json once for the whole update.
aistackregistry.com - zsh
_ ___ ____ _____ _ ____ _ __
/ \ |_ _| / ___| _ _|/ \ / ___| |/ /
/ _ \ | | \___ \ | | / _ \| | | ' /
/ ___ \ | | ___) | | |/ ___ \ |___| . \
/_/ \_\___| |____/ |_/_/ \_\____|_|\_\
Update all your AI model ids with one agent skill
Point Codex, Claude Code, OpenCode, or any CLI app to one URL and update all your repos at once.
38 models. 7 providers. ONE FETCH.
How one update runs
Provider docs and model IDs change. The catalog puts current model facts, connection settings, and first-party source links in one JSON response.
Check every repo
The agent reuses the same catalog as it checks model settings across your repositories.
You approve the edits
Review one plan per repo and apply the changes you want. Then run each repo's own checks.
Use the tool you already have
Codex or Claude Code
Put one instruction in AGENTS.md for Codex or CLAUDE.md for Claude Code, or
install the shared skill.
CI
Fetch /index.json in a read-only job and compare the model IDs, limits, and provider
settings your repo pins.
Check the first-party sources.
Each model entry links to the provider documentation used to verify it. A fact that documentation leaves out stays out of the entry.
Inspect the catalogQuestions developers ask
- Does this update my repos by itself?
- No. Give Codex or Claude Code a target model, review the plan, then approve the edits. Run the same process whenever a model changes.
- Does my agent need provider API keys?
- No. The catalog already contains provider connection settings and model facts. Your update job does not call model providers.
- Why not send every agent to provider docs?
- That repeats the same calls for every repo and can give each update a different answer. Fetch one catalog and reuse it across the whole update.
- Can CI use it?
- Yes. The setup page has a job that checks a configured model ID against the catalog.