Model Registry Maintainer
Microck/ordinary-claude-skills
Guide for maintaining the MassGen model and backend registry.
Add, change or verify a Nexus LLM model definition — the registry entry, the provider default, and proof the model id actually works against the live endpoint.
Install Nexus Model Updates
$ npx skills add ProfSynapse/nexus --skill nexus-model-updates -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ProfSynapse/nexus nexus-model-updates --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.skills/nexus-model-updates .claude/skills/nexus-model-updates && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nexus-model-updates" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-model-updates into .claude/skills/nexus-model-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-model-updates", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-model-updatesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ProfSynapse/nexus --skill nexus-model-updates -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ProfSynapse/nexus nexus-model-updates --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.skills/nexus-model-updates .agents/skills/nexus-model-updates && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nexus-model-updates" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-model-updates into .agents/skills/nexus-model-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-model-updates", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ProfSynapse/nexus --skill nexus-model-updates -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ProfSynapse/nexus nexus-model-updates --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.skills/nexus-model-updates .cursor/skills/nexus-model-updates && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nexus-model-updates" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-model-updates into .cursor/skills/nexus-model-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-model-updates", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ProfSynapse/nexus.git --path .skills/nexus-model-updates--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ProfSynapse/nexus --skill nexus-model-updates -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ProfSynapse/nexus nexus-model-updates --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.skills/nexus-model-updates .gemini/skills/nexus-model-updates && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nexus-model-updates" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-model-updates into .gemini/skills/nexus-model-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-model-updates", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ProfSynapse/nexus nexus-model-updatesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ProfSynapse/nexus --skill nexus-model-updates -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.skills/nexus-model-updates .github/skills/nexus-model-updates && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nexus-model-updates" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-model-updates into .github/skills/nexus-model-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-model-updates", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ProfSynapse/nexus --skill nexus-model-updates -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ProfSynapse/nexus nexus-model-updates --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.skills/nexus-model-updates .opencode/skills/nexus-model-updates && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nexus-model-updates" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-model-updates into .opencode/skills/nexus-model-updates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-model-updates", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
nexus-model-updates- GitHub stars
- 154
- Token cost
- ~1.1k tokens
- SKILL.md length
- 533 words
- Files
- 15 (incl. scripts, references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Add, change or verify a Nexus LLM model definition — the registry entry, the provider default, and proof the model id actually works against the live endpoint.
- Works in 7 steps: A model in a provider that already has a… → Moving a provider's default — follow… → A provider with no registry yet — follow → …
- Adding a newly released model
- SKILL.md covers Workflow, Map, Siblings — do not duplicate… and Refine
- Runs Python scripts from its folder; calls python3
What it does
Nexus Model Updates is an agent skill from ProfSynapse/nexus. Add, change or verify a Nexus LLM model definition — the registry entry, the provider default, and proof the model id actually works against the live endpoint. Use when adding a newly released model, editing model metadata such as pricing, context window or capability flags, promoting a provider default, standing up a model registry for a new provider, or checking whether a model id resolves through the live provider smoke lane.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files, including scripts and reference files (for example `agents/openai.yaml`, `protocols/add-image-model.md` and `protocols/add-model.md`).
It sits in Agent Workflows, covering Context engineering and MLOps. The licence is MIT.
When your agent uses it
- Adding a newly released model
- Editing model metadata such as pricing
- Capability flags
- Promoting a provider default
Example prompts
- “/nexus-model-updates”
Requirements
- Python 3
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- A model in a provider that already has a registry — follow
- Moving a provider's default — follow protocols/change-default.md. The
- A provider with no registry yet — follow
- An image generation model — follow protocols/add-image-model.md. Image
- A Live / realtime voice model (Google *-live*, OpenAI gpt-realtime*)
- Before calling any of the above done — run protocols/verify-model.md. You
- End of a session that used this skill — run protocols/self-refine.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 6cb7bce. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nexus Model Updates loads about 1.1k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 113 tokens; SKILL.md has 533 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from ProfSynapse/nexus at commit 6cb7bce, republished under its MIT licence (© ProfSynapse). 533 words, ~1,125 tokens.
Download SKILL.mdSave it as
.claude/skills/nexus-model-updates/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.- name
- nexus-model-updates
- description
- Add, change or verify a Nexus LLM model definition — the registry entry, the provider default, and proof the model id actually works against the live endpoint. Use when adding a newly released model, editing model metadata such as pricing, context window or capability flags, promoting a provider default, standing up a model registry for a new provider, or checking whether a model id resolves through the live provider smoke lane.
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 . --listWorkflow
- 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 tonexus-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 Live / realtime voice model (Google
*-live*, OpenAIgpt-realtime*) — followprotocols/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 fromscripts/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.
Show full SKILL.md (207 more words)Show less
Map
protocols/the procedures: add-model, add-image-model, add-realtime-voice-model, change-default, add-provider-registry, verify-model, self-refine.references/mechanism, read on demand:registry-anatomy.md(what aModelSpecfield means and how to fill it),consumers.md(who reads the registries and what silently breaks when metadata is wrong),smoke-harness.md(the live provider smoke lane in detail),provider-listings.md(how to ask a provider what it serves right now — run this before saying a model does not exist).scripts/check_model_registry.py— the structural gate: required fields, provider/directory agreement, unreachable duplicate ids, defaults that point at nothing, adapter literals that drifted from the registry, and registries wired into one aggregator but not the other. Run it; do not re-derive it by reading source.
Siblings — do not duplicate them here
nexus-llm-adaptersowns adapter wiring: transport, streaming, reasoning rendering, and the provider registration points outside the model catalog.nexus-model-evalowns grading a model on Nexus tool use. A smoke test proves the id returns text; it proves nothing about tool calling, and a model that passes smoke can still be unusable in chat.nexus-eval-harnessowns running and changing the eval harness itself.nexus-testingowns which Jest lane to use and what a mock can prove.
Refine
At the end of a session that used this skill, run protocols/self-refine.md and
append to refinement-log.md.
© ProfSynapse, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 14 other files (scripts, references) in .skills/nexus-model-updates of ProfSynapse/nexus.
- SKILL.md
- agents/openai.yaml
- protocols/add-image-model.md
- protocols/add-model.md
- protocols/add-provider-registry.md
- protocols/add-realtime-voice-model.md
- protocols/change-default.md
- protocols/self-refine.md
- protocols/verify-model.md
- references/consumers.md
- references/provider-listings.md
- references/registry-anatomy.md
- references/smoke-harness.md
- refinement-log.md
- scripts/check_model_registry.py
Open the folder on GitHubat commit 6cb7bce
Compare with similar skills
Nexus Model Updates next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nexus Model Updates this skillProfSynapse/nexus | 154 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Model Registry MaintainerMicrock/ordinary-claude-skills | 401 | — | ~3.6k | Automated safety check: Pass | Custom licence | |
| Context Mode Output Sandboxmksglu/context-mode | 26k | — | ~4.1k | Automated safety check: Pass | Custom licence | |
| Memori Long-Term MemoryMemoriLabs/Memori | 17k | — | ~2k | Automated safety check: Notes | Custom licence | |
| Picoclaw Skill Creatorsipeed/picoclaw | 30k | — | ~4.4k | Automated safety check: Pass | MIT | |
| ccc Semantic Code Searchcocoindex-io/cocoindex-code | 2.7k | — | ~938 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Context Mode Output Sandbox
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
Memori Long-Term Memory
MemoriLabs/Memori
Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.
Picoclaw Skill Creator
sipeed/picoclaw
Guidance for creating, updating and reviewing Picoclaw skills, from the SKILL.md structure to organizing bundled scripts, references and assets.
ccc Semantic Code Search
cocoindex-io/cocoindex-code
Semantic code search and index management with the ccc CLI: the agent initializes, indexes and queries the project by concept, filtering by language or path.
Context Mode for Antigravity CLI
mksglu/context-mode
Routing rules for using context-mode MCP tools in Antigravity CLI: sandboxed code runs, file analysis, indexed search and web fetches that keep large output out of the conversation.
More from ProfSynapse/nexus
All 12 skills in this repoNexus Agents
ProfSynapse/nexus
How to add, change and verify a Nexus agent or tool, and the contract every tool must satisfy.
Nexus Eval Harness
ProfSynapse/nexus
Work on the Nexus LLM eval harness in tests/eval/ — author or fix a scenario fixture, write an eval config, change the executors, assertions or reports, or explain a run that produced nothing…
Nexus Model Eval
ProfSynapse/nexus
Grade how well a model drives the Nexus two-tool protocol (getTools/useTools) and decide whether a low score is the model's fault or the harness's.
Nexus Release
ProfSynapse/nexus
Cut a Nexus release — bump the version with the repo's own machinery, get the docs and generated sources right, push a tag the GitHub Actions workflow will actually pick up, and recover when it does…
Nexus Storage
ProfSynapse/nexus
How to change, persist, migrate and recover Nexus data without losing it.
Nexus Testing
ProfSynapse/nexus
Verify a Nexus change — pick a Jest lane, write a test that can actually fail, run the in-app Obsidian CLI loop, drive the eval harness, or fix a shipped-docs drift failure.
Related
Categories
Questions about Nexus Model Updates
What does Nexus Model Updates do?
Add, change or verify a Nexus LLM model definition — the registry entry, the provider default, and proof the model id actually works against the live endpoint. Nexus Model Updates is an agent skill from ProfSynapse/nexus. Add, change or verify a Nexus LLM model definition — the registry entry, the provider default, and proof the model id actually works against the live endpoint.
When should I use Nexus Model Updates?
Nexus Model Updates fits situations like: adding a newly released model; editing model metadata such as pricing; capability flags; promoting a provider default.
How do I install Nexus Model Updates in Claude Code?
Run `npx skills add ProfSynapse/nexus --skill nexus-model-updates -a claude-code`. Or copy the skill folder (.skills/nexus-model-updates in ProfSynapse/nexus) into .claude/skills/nexus-model-updates in your project. Claude Code loads it when a task matches its description.
How do I install Nexus Model Updates in Codex?
Run `npx skills add ProfSynapse/nexus --skill nexus-model-updates -a codex`. Or copy the skill folder (.skills/nexus-model-updates in ProfSynapse/nexus) into .agents/skills/nexus-model-updates in your project. Codex loads it when a task matches its description.
Can I use Nexus Model Updates in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ProfSynapse/nexus --skill nexus-model-updates -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nexus-model-updates, .gemini/skills/nexus-model-updates, .github/skills/nexus-model-updates and .opencode/skills/nexus-model-updates in your project.
What does Nexus Model Updates need to run?
Going by SKILL.md and its folder, Nexus Model Updates needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Nexus Model Updates access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Nexus Model Updates safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Nexus Model Updates use?
Nexus Model Updates is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nexus Model Updates use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.8k tokens, read only when the agent opens those files.
What are the alternatives to Nexus Model Updates?
Skills that share tags, products or a category with Nexus Model Updates: Model Registry Maintainer (Microck/ordinary-claude-skills, 401 stars), Context Mode Output Sandbox (mksglu/context-mode, 26k stars), Memori Long-Term Memory (MemoriLabs/Memori, 17k stars) and Picoclaw Skill Creator (sipeed/picoclaw, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nexus Model Updates?
ProfSynapse (a GitHub user) maintains it in ProfSynapse/nexus, which has 154 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 2, 2026.
Source: ProfSynapse/nexus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.