Borrowing it
Nothing to install: this file belongs to Joouis/agent-maestro. 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/Joouis/agent-maestro/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/Joouis/agent-maestroWrote 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/joouis/agent-maestro/release)<a href="https://agentmods.dev/commands/joouis/agent-maestro/release"><img src="https://agentmods.dev/badge/commands/joouis/agent-maestro/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/joouis/agent-maestro/release"><img src="https://agentmods.dev/badge/commands/joouis/agent-maestro/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.00019 | $0.00299 |
| Opus 5.5 | $0.00008 | $0.00120 |
| Sonnet 5.5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
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 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.
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.
What it actually says
Release Process
Follow AGENTS.md. Begin only when a release is requested, and verify a clean worktree so unrelated changes cannot enter the release.
Prepare
git status --short
git switch main
git pull --ff-only origin main
pnpm changeset:version
Read the resulting version from package.json, then create release/v{VERSION} using that exact version. The version command updates package metadata/changelog and consumes pending changesets; do not edit version fields independently.
Review
- Inspect every changed file and verify the version and release notes.
- Keep notes focused on user-visible behavior; preserve older changelog history.
- Run checks appropriate to any release edits.
- Discuss the concrete changelog with the user before committing unless that review step was explicitly waived.
Commit and Publish the Branch
Stage only the reviewed release files, including consumed changeset deletions. Inspect git diff --cached before committing with chore: release v{VERSION}. Use actual contributor attribution only; do not add a fixed agent identity.
Push the release branch only with the user's authorization. Create a PR against main with the release summary and validation. Branch publication and PR creation do not authorize Marketplace/Open VSX publication.
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 · -27 lines f9816860c89c
- 1mo ago First seen · 60 lines · 19 tokens per session scan A 660cfd53b079
release is a command published in the GitHub repository Joouis/agent-maestro (209 stars, last pushed 13d ago), licensed MIT. It adds 19 tokens to every session and 299 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.