Borrowing it
Nothing to install: this file belongs to AgentSystemLabs/nebula. 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/AgentSystemLabs/nebula/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/AgentSystemLabs/nebulaWrote 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/agentsystemlabs/nebula/release)<a href="https://agentmods.dev/skills/agentsystemlabs/nebula/release"><img src="https://agentmods.dev/badge/skills/agentsystemlabs/nebula/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/agentsystemlabs/nebula/release"><img src="https://agentmods.dev/badge/skills/agentsystemlabs/nebula/release.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.00110 | $0.03766 |
| Opus 5.5 | $0.00044 | $0.01506 |
| Sonnet 5.5 | $0.00022 | $0.00753 |
| Haiku 4.5 | $0.00011 | $0.00377 |
Grade C, and why
release scanned grade C with 2 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 1mo 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/AgentSystemLabs/nebula/main/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/AgentSystemLabs/nebula/main/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nebula releases are tag-driven: pushing a v* tag makes .github/workflows/release.yml build the
cross-compile matrix and publish a GitHub release with the binaries attached. Everything before the tag
push is your job; everything after it is CI's, except the changelog, which CI gets wrong.
Work through the steps in order. Do not skip the green gate. If the user only wants the release notes for a tag that already exists, jump to step 7.
1. Preflight — assume you are not alone in this tree
Other agents edit this repo concurrently, and they will fight you for the index. All of these have happened while cutting a release:
- Files you never opened turn up modified mid-task (
git statusfrom two minutes ago proves nothing). git addsilently captures their half-finished edits to a file you also touched — the staged diff came back 66 lines when the change under review was 56.- The index gets reset out from under a staged commit, so
git commitreports "no changes added". - A
git worktreeyou created gets pruned away underneath you.
So do not stage in the shared index at all. Do the entire release in a private worktree on a branch,
and push that branch to main. The shared working tree is never touched, and nothing another agent
does can corrupt what you are about to tag.
git fetch origin
W=<scratchpad>/release
git worktree add -b release-vX.Y.Z "$W" origin/main
A release-vX.Y.Z branch that already exists is a prior attempt from another session's scratchpad
(git worktree list); git branch -m it aside and cut fresh.
Then bring your change in by content, file by file, checking each one as you go:
git -C <repo> diff -- <file> # read it: is every hunk yours?
cp <repo>/<file> "$W"/<file>
A plain cp is only safe when the shared checkout's HEAD is origin/main
(git rev-list --left-right --count HEAD...origin/main prints 0 0); otherwise a blind copy reverts
whatever origin merged since, so carry the change as a --3way patch instead. For a file where your
change is tangled with someone else's, extract only your hunks (git diff -- <file> > all.patch, keep
your @@ blocks, git apply them onto the pristine copy) and re-read the result.
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.
- 1mo ago Changed 66b70c73d2ea
- 1mo ago Changed · +36 lines · +22 tokens per session scan D → C 2f6b74d0dc6d
- 1mo ago First seen · 220 lines · 88 tokens per session scan D 0561ec9394a4
release is a skill published in the GitHub repository AgentSystemLabs/nebula (272 stars, last pushed 6d ago), licensed MIT. It adds 110 tokens to every session and 3,766 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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.