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/agentsystemlabs/nebula/releasenpx skills add AgentSystemLabs/nebula --skill releasegit clone --depth 1 https://github.com/AgentSystemLabs/nebulaWhat 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.03006 |
| Opus 5 | $0.00044 | $0.01503 |
| Sonnet 5 | $0.00018 | $0.00601 |
| Haiku 4.5 | $0.00009 | $0.00301 |
Grade D, and why
release scanned grade D with 3 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 3d 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 Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
re-read the result. Read the RELEASE SKILL group of `.claude/memory/gotchas.md` and grep `.claude/memory/entries` for the subsystem you're releasing. 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 — 220 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.
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 three of these happened while cutting v0.3.0:
- 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
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>
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. Read the RELEASE SKILL group of .claude/memory/gotchas.md and grep .claude/memory/entries for the subsystem you're releasing.
2. Green gate — the tag must point at code that compiles
In the worktree, with a separate CARGO_TARGET_DIR (sharing the main one with a concurrently
building session makes both of you thrash fingerprints and rebuild from scratch):
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.
- 3d ago First seen · 220 lines · 88 tokens per session scan D 0561ec9394a4
release is a skill published in the GitHub repository AgentSystemLabs/nebula (100 stars, last pushed 2d ago), licensed MIT. It adds 88 tokens to every session and 3,006 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 3 findings (downloads and executes remote code, reads agent configuration directories, 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.