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 commands/gaia-react/gaia/gaia-releasegit 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.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.06396 |
| Opus 5 | $0.00017 | $0.03198 |
| Sonnet 5 | $0.00007 | $0.01279 |
| Haiku 4.5 | $0.00003 | $0.00640 |
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 5d 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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, both this slash command and the gaia-maintainer binary are stripped from distributed tarballs by .gaia/release-exclude so adopters never see them. The adopter gaia binary has no release namespace at all; only gaia-maintainer does. Unlike /gaia-init, this command does not self-delete; it runs every release.
[!important]
mainis protected Direct pushes tomainare blocked. The release commit lands on arelease/v<NEW_VERSION>branch, goes through a PR, and the tag is created on the merge 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 the version and rebundles both CLI binaries, so it always touches.gaia/cli/**and always runs that job's full typecheck, lint, vitest, and bundle-freshness path rather than its filter-miss fast pass.gh pr merge --merge --autois the normal path: base-branch protection rejects a plain--merge, 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.
- 5d ago First seen · 353 lines · 34 tokens per session scan A 23ecd2cf01ca
gaia-release is a command published in the GitHub repository gaia-react/gaia (23 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 6,396 once invoked, about $0.0002 per session on Opus 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
pr-description
Generate a pull request description based on the changes in the current branch.
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.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
security-sast
Static Application Security Testing (SAST) for code vulnerability analysis across multiple languages and frameworks.
add-python-dependencies
Add helpful Python dependencies to the current uv project.