update-nexus

update-nexus is a skill for Claude Code, Codex from DorianSchlede/nexus-template. It costs 17 tokens per session (832 once invoked), scanned A, original, MIT.

An updater that synchronizes Nexus system files and documentation with their upstream repository while preserving your personal workspace data and settings.

In plain words
What is it for?
Use it to check for Nexus updates, review the files that would change, and apply approved system updates.
Why use it?
It reduces the risk of manually updating framework files or accidentally overwriting your goals, builds, custom skills, and secrets.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md.

Good fit Use it to check for Nexus updates, review the files that would change, and apply approved system updates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dorianschlede/nexus-template/update-nexus
Install

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.

Any agent
npx skills add DorianSchlede/nexus-template --skill update-nexus
Clone the repo
git clone --depth 1 https://github.com/DorianSchlede/nexus-template

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.

agentmods badge for update-nexus

README.md
[![agentmods](https://agentmods.dev/badge/skills/dorianschlede/nexus-template/update-nexus/github.svg)](https://agentmods.dev/skills/dorianschlede/nexus-template/update-nexus)
Your own site
<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/update-nexus"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/update-nexus/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.

agentmods 80×15 button for update-nexus

Your own site · 80×15
<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/update-nexus"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/update-nexus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 832 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00832
Opus 5 $0.00009 $0.00416
Sonnet 5 $0.00003 $0.00166
Haiku 4.5 $0.00002 $0.00083

Measured 8d ago against content hash e4d571fca4a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

update-nexus 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 8d ago.

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.

00-system/skills/system/update-nexus/SKILL.md · 130 lines

How it starts

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

Update Nexus

Purpose: Sync system files from the upstream Nexus repository while protecting user data

Trigger: "update nexus", "sync nexus", "get updates", "check for updates"

Duration: 1-2 minutes


What This Does

Updates these system files from upstream:

  • 00-system/ - Core framework, skills, documentation
  • CLAUDE.md - Entry point
  • README.md - Build readme

Protects these user folders (NEVER touched):

  • 01-memory/ - Your goals, learnings, config
  • 02-builds/ - Your builds
  • 03-skills/ - Your custom skills
  • 04-workspace/ - Your files
  • .env, .claude/ - Your secrets and settings

Workflow

Step 1: Check for Updates

Run the update check:

nexus-load --check-update

Parse the JSON response:

  • If checked: false with error → Display error, exit gracefully
  • If update_available: false → Display "Already up-to-date!", exit
  • If update_available: true → Continue to Step 2

Step 2: Show What Will Change

Display to user:

UPDATE AVAILABLE

Current version: {local_version}
New version:     {upstream_version}

Files to update ({changes_count}):
{list changed_files, max 20}

PROTECTED (will NOT be touched):
- 01-memory/    (your goals & config)
- 02-builds/  (your builds)
- 03-skills/    (your custom skills)
- 04-workspace/ (your files)

Step 3: Confirm with User

Ask: "Proceed with update? (yes/no)"

  • If no → Exit with "Update cancelled"
  • If yes → Continue to Step 4

Step 4: Perform Sync

Run the sync command:

nexus-load --sync --force

Parse the JSON response:

  • If success: false → Display error message, suggest fixes
  • If success: true → Continue to Step 5

Step 5: Display Results

On success, display:

UPDATE COMPLETE!

{local_version} → {upstream_version}

Updated paths:
{list files_updated}

Backup saved to: {backup_path}

To commit this update:
  git add . && git commit -m "Update Nexus to v{upstream_version}"

Error Handling

Read the full file on GitHub · 130 lines

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.

  1. 8d ago First seen · 130 lines · 17 tokens per session scan A e4d571fca4a1

Subscribe to this mod's changes

update-nexus is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 832 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens