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 skills add DorianSchlede/nexus-template --skill update-nexusgit clone --depth 1 https://github.com/DorianSchlede/nexus-templateWrote 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/dorianschlede/nexus-template/update-nexus)<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.
<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>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.00017 | $0.00832 |
| Opus 5 | $0.00009 | $0.00416 |
| Sonnet 5 | $0.00003 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
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.
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, documentationCLAUDE.md- Entry pointREADME.md- Build readme
Protects these user folders (NEVER touched):
01-memory/- Your goals, learnings, config02-builds/- Your builds03-skills/- Your custom skills04-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: falsewith 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
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.
- 8d ago First seen · 130 lines · 17 tokens per session scan A e4d571fca4a1
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.
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.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
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.
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.
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".
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…