Borrowing it
Nothing to install: this file belongs to gaia-react/gaia. 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/gaia-react/gaia/main/.claude/commands/gaia-release.mdgit clone --depth 1 https://github.com/gaia-react/gaiaWrote 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/commands/gaia-react/gaia/gaia-release)<a href="https://agentmods.dev/commands/gaia-react/gaia/gaia-release"><img src="https://agentmods.dev/badge/commands/gaia-react/gaia/gaia-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/commands/gaia-react/gaia/gaia-release"><img src="https://agentmods.dev/badge/commands/gaia-react/gaia/gaia-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.00040 | $0.06715 |
| Opus 5.5 | $0.00016 | $0.02686 |
| Sonnet 5.5 | $0.00008 | $0.01343 |
| Haiku 4.5 | $0.00004 | $0.00671 |
Grade A, and why
gaia-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 4d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contents: Required argument; Pre-flight: Worktree check; Workflow; Recovery: I tagged on the wrong commit.
Cut a new GAIA release. Thin orchestrator over the .gaia/cli/gaia-maintainer release CLI namespace, which owns every deterministic step (preflight checks, semver bump, CHANGELOG graduation, wiki scrub, manifest regen, commit + tag dance). This command sequences the CLI subcommands and surfaces user-facing prompts where human judgment is required.
This command is maintainer-only: it and the gaia-maintainer binary are release-excluded.
[!important]
mainis protected Direct pushes tomainare blocked. The release commit lands on a release branch, goes through a PR, and the tag is created on the squash commit after it lands onmain. The release PR is subject to the same CI gate and the same Code Audit Team merge handshake as any other PR. ExpectVitest and Playwright,Run Chromatic, andVitest (.gaia/cli): a release PR bumps rootpackage.json, which that job's paths filter lists, so it always runs the job's full typecheck, lint, vitest, and bundle-freshness path rather than its filter-miss fast pass (it touches.gaia/cli/**only when Step 7b rebuilt the bundles).gh pr merge --squash --autois the normal path: the repository allows squash merges only, and base-branch protection rejects a merge without--auto, so--autois required to queue the merge until checks pass. Seewiki/concepts/PR Merge Workflow.md.
Required argument
Invocation: /gaia-release patch|minor|major. The argument is the sole authority for the version bump.
If the argument is missing, including when /gaia-release is reached as part of a larger batch of work ("ship this then release", a multi-step plan that ends in release, a chained workflow), STOP and ask the maintainer via AskUserQuestion before any preflight / branch / commit step. Do not infer the bump from commit prefixes, diff size, or the gaia-maintainer release bump proposal.
The conventional-commit scan over-proposes minor for CI/plumbing commits incorrectly tagged feat: that are patch-level in spirit; the maintainer is the only reliable source for semver intent. Never proceed without an explicit patch|minor|major from the maintainer.
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.
- 4d ago Changed · +12 lines 13762132c71b
- 5d ago Changed cd6ad4b3ef71
- 6d ago Changed · -21 lines bfd918f35aa2
- 8d ago Changed · +4 lines 95bd47458b07
- 10d ago Changed · -2 lines 7baf7704f85d
- 11d ago Changed · +1 lines 2c34371b283e
- 12d ago Changed e4152fa947ec
- 13d ago Changed 5d84929a4193
- 14d ago Changed · +2 lines 64579b66050b
- 15d ago First seen · 372 lines · 40 tokens per session scan A 923b6fdbd906
gaia-release is a command published in the GitHub repository gaia-react/gaia (26 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 6,715 once invoked, about $0.0002 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 commands, from other repositories
push-changes
If no topic provided, just document the recent changes. If a topic is provided, focus on documenting that topic.
create-PR
Command "create-PR" from bartstc/vite-ts-react-template, covering create a pr against this branch: $arguments, follow these steps and remember.
implement-feature
Implement an approved feature plan with benefit-based placement, TDD, revision-bound evidence, and PR-ready output.
deploy-release
Prepare and verify a staged or production deployment with rollback and smoke checks.
fork-discipline
Audit and enforce the core/client boundary in multi-client codebases.
release
Prepare and publish a GitHub release.