What is nexus-model-updates?

A workflow for adding, changing, or checking the model definitions used by the Nexus application. A model definition records details such as a provider's model ID, price, context size, and supported capabilities.

Use it when adding a newly released language model, updating its metadata, changing a provider's default model, or adding a provider without an existing registry.

It reduces mistakes caused by editing only one of the several registries that control model selection, pricing, defaults, and interface options. It also requires checking that a model ID works with the live provider endpoint.

How ProfSynapse/nexus configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to ProfSynapse/nexus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ProfSynapse/nexus/main/.claude/skills/nexus-model-updates/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ProfSynapse/nexus

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-model-updates/github.svg)](https://agentmods.dev/skills/profsynapse/nexus/nexus-model-updates)

Your own site

<a href="https://agentmods.dev/skills/profsynapse/nexus/nexus-model-updates"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-model-updates/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/profsynapse/nexus/nexus-model-updates"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-model-updates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,137 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00088	$0.01137
Opus 5.5	$0.00035	$0.00455
Sonnet 5.5	$0.00018	$0.00227
Haiku 4.5	$0.00009	$0.00114

Measured 15d ago against content hash 45cc34e5bfc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

nexus-model-updates scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 15d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/check_model_registry.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/nexus-model-updates/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Nexus model updates

Each provider keeps a static model catalog at src/services/llm/adapters/<provider>/<Provider>Models.ts: an array of ModelSpec literals plus a *_DEFAULT_MODEL export. Two aggregators read those arrays, and between them they decide what the model picker offers, what a call costs, and which UI affordances appear.

Nothing here holds model ids, prices, context windows or provider lists — the registries are the truth and they change weekly. This skill holds the procedure and the checks. To see what the tree currently declares:

python3 .claude/skills/nexus-model-updates/scripts/check_model_registry.py \
  --repo-root . --list

Workflow

A model in a provider that already has a registry — follow protocols/add-model.md. Get every number from the provider's own source; values carried over from another gateway's entry are wrong more often than they are right.
Moving a provider's default — follow protocols/change-default.md. The default is written in several independent places and TypeScript checks none of them against each other, so you MUST work that protocol rather than editing the one you happened to find.
A provider with no registry yet — follow protocols/add-provider-registry.md. Adapter wiring belongs to nexus-llm-adapters; only the catalog and its aggregator entries are yours.
An image generation model — follow protocols/add-image-model.md. Image models live in the image adapters' own catalogs, not in <Provider>Models.ts, the structural gate does not see them, and the committed tool catalogs embed their enum.
A video generation model — follow protocols/add-video-model.md. They live in one static array in src/services/llm/types/VideoTypes.ts. The structural gate does not see them, and an id missing from that array is rejected even when the provider lists it.
A Live / realtime voice model (Google *-live*, OpenAI gpt-realtime*) — follow protocols/add-realtime-voice-model.md. These ids answer only over a WebSocket session, so they do not belong in <Provider>Models.ts, the structural gate does not see them, and the provider smoke lane cannot prove them; the realtime smoke lane drives the shipped session instead.
Before calling any of the above done — run protocols/verify-model.md. You MUST get a zero exit from scripts/check_model_registry.py --repo-root . <provider>, and you MUST NOT report a model as working on the strength of a registry entry: the entry is a claim about an id, and only a live call tests it.
End of a session that used this skill — run protocols/self-refine.md.

Read the full file on GitHub · 83 lines

Files

What ships with it

15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

15d ago Changed · +4 lines 45cc34e5bfc4
1mo ago Changed · +2 lines 288ec61229f2
1mo ago Changed · +6 lines 1955a54e4090
1mo ago Changed · +4 lines 344bb2c1f3fd
2mo ago First seen · 67 lines · 88 tokens per session scan A 70a41d472100

Subscribe to this mod's changes

nexus-model-updates is a skill published in the GitHub repository ProfSynapse/nexus (158 stars, last pushed 5d ago), licensed MIT. It adds 88 tokens to every session and 1,137 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Data and AI

agent-platform-model-registry

Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.

google/skills · 60 tokens

foundry-config-setup

Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.

microsoft/agent-framework · 65 tokens

google-cloud-solution-agentic-analytics-spark-knowledge-catalog

Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and…

google/skills · 132 tokens

training-check

Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.

wanshuiyin/Auto-claude-code-research-in-sleep · 35 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

finetuning

Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file…

microsoft/skills · 132 tokens

nexus: Skill for Claude Code