Borrowing it
Nothing to install: this file belongs to Hackbyrd/orbital-express. 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/Hackbyrd/orbital-express/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/Hackbyrd/orbital-expressWrote 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/hackbyrd/orbital-express/release)<a href="https://agentmods.dev/skills/hackbyrd/orbital-express/release"><img src="https://agentmods.dev/badge/skills/hackbyrd/orbital-express/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/hackbyrd/orbital-express/release"><img src="https://agentmods.dev/badge/skills/hackbyrd/orbital-express/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.00112 | $0.01161 |
| Opus 5.5 | $0.00045 | $0.00464 |
| Sonnet 5.5 | $0.00022 | $0.00232 |
| Haiku 4.5 | $0.00011 | $0.00116 |
Grade A, and why
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
Walk the user through cutting a new Orbital Express release from start to finish.
The full process reference is at docs/release-guide.md.
Step 1 — Read the current state
Before asking anything, read:
package.json→ get the current versionCHANGELOG.md→ see the last release entry so you know what's already logged
Step 2 — Ask: what kind of release?
Tell the user the current version and suggest the three options with the bumped number for each:
Current version is 3.0.0. What kind of release is this?
- Patch
3.0.1— bug fix, doc correction, small tweak- Minor
3.1.0— new feature, non-breaking addition- Major
4.0.0— breaking change or full rewrite
Wait for their answer, then confirm the new version number you'll use.
Step 3 — Collect what changed
Ask the user to describe what changed. Walk through each section one at a time — only ask about sections that might be relevant. You don't need all of them; skip any the user says are empty.
Ask in this order:
- Added — new things that didn't exist before
- Changed — existing things that behave differently
- Fixed — bugs that were broken and are now working
- Removed — things that no longer exist
- Breaking Changes — anything that requires users to update their code (only ask if major or if the user mentioned something breaking)
For each section, let the user describe in their own words — you will clean up and format the bullet points. Keep entries concise: one line per item, lead with the thing in bold, follow with a short description after the dash.
Example of good formatting:
middleware/exit.js— graceful shutdown now waits up to 30s before force-exiting- Route URL convention — all lowercase, no separators (
V1LogoutAll→/v1/users/logoutall)
Also ask for a one-sentence Overview that summarizes what this release is about. This goes at the top of the entry.
Step 4 — Write a summary and confirm
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 · 131 lines · 112 tokens per session scan A 86d8ca20c3b5
release is a skill published in the GitHub repository Hackbyrd/orbital-express (15 stars, last pushed 2mo ago), licensed MIT. It adds 112 tokens to every session and 1,161 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-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.
release
Fully automate a release with version-bump and childhood.
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.