Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/profsynapse/nexus/nexus-model-updatesnpx skills add ProfSynapse/nexus --skill nexus-model-updatesgit clone --depth 1 https://github.com/ProfSynapse/nexusWrote 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.
[](https://agentmods.dev/skills/profsynapse/nexus/nexus-model-updates)<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="Measured on agentmods" height="20"></a>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 | $0.00088 | $0.00933 |
| Opus 5 | $0.00044 | $0.00466 |
| Sonnet 5 | $0.00018 | $0.00187 |
| Haiku 4.5 | $0.00009 | $0.00093 |
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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 71 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 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. - 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.
What ships with it
12 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.
- agents/openai.yaml 225 B
- protocols/add-image-model.md 5.2 KB
- protocols/add-model.md 5.4 KB
- protocols/add-provider-registry.md 3.5 KB
- protocols/change-default.md 5.9 KB
- protocols/self-refine.md 2.7 KB
- protocols/verify-model.md 3.8 KB
- references/consumers.md 4.0 KB
- references/registry-anatomy.md 6.4 KB
- references/smoke-harness.md 5.2 KB
- refinement-log.md 6.4 KB
- scripts/check_model_registry.py 18 KB runs code
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.
- today Changed · +4 lines 344bb2c1f3fd
- 4d ago First seen · 67 lines · 88 tokens per session scan A 70a41d472100
nexus-model-updates is a skill published in the GitHub repository ProfSynapse/nexus (154 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 933 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
crewai
Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (sequential, hierarchical, parallel), memory systems, and flows for complex workflows. Essential for building collaborative…
optimization
Use when improving performance, latency, throughput, memory usage, or general efficiency. Start by defining target metrics, measuring comprehensively, attributing bottlenecks, validating with static analysis, and prioritizing macro-optimizations before micro-optimizations.
hivemind-graph
Query the local code graph (functions, classes, calls, imports) through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what's the architecture / which subsystems exist?", "what's the impact of…
mantis-threat-model
Synthesizes trust boundaries, attack surfaces, and attacker profiles into a living threat model. Use as Stage B of the Knowledge Base generation process, reading architecture and entity definitions from the KB. Don't use for analyzing source code or extracting raw learnings from JSONL files.
wiki_capture
The knowledge base stores durable, reusable business knowledge for an analytics assistant. Each page is a self-contained rule, definition, or convention that answers "how should this concept be handled in this organization?" - written once and reused across chats.
rules
The 50 rules of natural language programming. Loaded when writing, reviewing, or improving any NL artifact — skills, agents, commands, rules, hooks, prompts, plugins, and the project memory file (CLAUDE.md / AGENTS.md / GEMINI.md). The definitive style guide for NL code quality.