model-catalogue-update
Skill12 starsChanged 29 days agoMITView on GitHub
Add, change or retire a model id in the routing catalogue. Use whenever a task touches config/models.yaml, config/llm/models.yaml, packages/ai/brain_config.py PROVIDER_CANDIDATES or presets, or packages/ai/cost_tracker.py prices — including the daily "new models" automation.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- agent/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- router/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/verification.mdcCursor rule
- agentic-agileSkill
- agentic-portfolioSkill
- client-onboardingSkill
- cooldown-resumeSkill
- drillSkill
- ecc-harness-patternsSkill
- fabric-patternsSkill
- graphiti-temporalSkill
- managed-agents-dreamsSkill
- platform-setupSkill
- repowise-intelligenceSkill
- risky-module-reviewSkill
- seo-audit-reportSkill
- user-researchSkill
- video-contextSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Never duplicate a key: Search the dict or YAML for the id before adding it.
- Distinctive: line 35
Prove it: Run, and paste the summary line of:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Model catalogue update
The catalogue decides what the agency routes to in production. A wrong id costs every call that lands on it, so the rules below are not style.
- Check the retired list first.
RETIREDintests/test_nvidia_default_model.pyand theremoved …/(404)/(410)comments inconfig/models.yamlname ids that failed live on this account. Do not re-add one. A vendor page saying the model exists is not evidence it answers here: #1695 (Nemotron 3.5 Lightning) and #1697 (Llama 3.3 Nemotron Super 49B) both re-added retired ids from vendor docs and went red. - Never duplicate a key. Search the dict or YAML for the id before adding it; a duplicate silently overwrites the earlier entry (#1689).
- Unprobed means explicit-only. A new id gets
priority: 99, stays out ofPROVIDER_CANDIDATESand every preset, and its cost entry says it is an estimate until a probe (catalogue-probe.yml) has seen HTTP 200 with a real completion. - Mirror both configs.
config/models.yamlandbrain_config.pymust agree;test_yaml_presets_mirror_brain_configchecks it. Prove it. Run, and paste the summary line of:
pytest -q tests/test_one_model_catalogue.py tests/test_nvidia_default_model.py tests/test_model_router.py
The pre-PR gate (agent/pr_gate.py) runs these suites whenever model config changes,
so an agent PR that breaks rule 1 or 2 does not open. This skill is the advisory half;
the gate is the deterministic half.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

