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.
curl -O https://raw.githubusercontent.com/ProfSynapse/nexus/main/.claude/skills/nexus-release/SKILL.mdgit 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-release)<a href="https://agentmods.dev/skills/profsynapse/nexus/nexus-release"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-release/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/profsynapse/nexus/nexus-release"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.00940 |
| Opus 5.5 | $0.00036 | $0.00376 |
| Sonnet 5.5 | $0.00018 | $0.00188 |
| Haiku 4.5 | $0.00009 | $0.00094 |
Grade A, and why
nexus-release 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 2mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nexus Release
Context: a Nexus release is one artifact — a bare X.Y.Z git tag on main.
Everything downstream (installing, building, naming the release, uploading
main.js / manifest.json / styles.css, provenance attestation) is done by
<repo>/.github/workflows/release.yml from the tagged commit. You never build
the release; you make the tagged commit correct and then tag it.
Two consequences shape everything here. The tag is the point of no return — the workflow reads the tree as committed at that tag. And the workflow guards only three things, so everything else is on you.
Path convention: <repo>/… means relative to the Nexus repo root. Bare paths
(protocols/…, scripts/…) are inside this skill.
Workflow
-
Cutting a release → follow
protocols/cut-release.mdend to end, in order. Do not improvise the sequence: several steps only have any effect before the tag exists. -
Bringing user-facing docs in line (a phase of the above; also runnable on its own) →
protocols/doc-review.md. -
Before pushing any tag you MUST get a clean exit from the readiness check. It reproduces the workflow's own version guard locally, so a failure here is a failure you would otherwise discover after the tag exists:
python3 .claude/skills/nexus-release/scripts/check_release_ready.py --tag X.Y.Z(
--repodefaults to the repo root found by walking up from the working directory. Run--helpfor the flags; stdlib only, nonode_modules. If the mirror above is absent, the same file is at<repo>/.skills/nexus-release/scripts/check_release_ready.py.) -
The workflow did not run, failed its guard, or shipped the wrong assets →
protocols/recover.md. NEVER hand-create a release or hand-attach assets to fix it — that silently drops provenance attestation. -
After a release session →
protocols/self-refine.md.
Map
protocols/the how:cut-release.md,doc-review.md,recover.md,self-refine.md.references/the why, read on demand:release-machinery.md(what the workflow really does, what it guards, what it does not, and the build-order asymmetry that decides which generated file can ship stale),changelog-format.md(the conventions the changelog actually follows).scripts/check_release_ready.py— version consistency acrosspackage.json,manifest.json,versions.json, the lockfile and the tag.refinement-log.md— what past releases taught this skill.
What ships with it
8 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.
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.
- 2mo ago First seen · 75 lines · 90 tokens per session scan A 8eedb9fc230e
nexus-release is a skill published in the GitHub repository ProfSynapse/nexus (158 stars, last pushed 5d ago), licensed MIT. It adds 90 tokens to every session and 940 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.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.