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/joouis/agent-maestro/releasegit 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.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.00019 | $0.00330 |
| Opus 5 | $0.00010 | $0.00165 |
| Sonnet 5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
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 today.
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
Create a new release for the project following these steps:
1. Checkout and update main
git checkout main && git fetch origin && git pull origin main
2. Run changeset version
pnpm run changeset:version
3. Read new version and create release branch
- Read
package.jsonto get the new version number - Create release branch:
git checkout -b release/v{VERSION}
4. Review changes
- Check
git statusto see modified files - Review
CHANGELOG.mdfor accurate and clear entries - Verify version bump in
package.json - Discuss changelog with user before proceeding
5. Improve changelog if needed
- Ensure entries describe user impact, not just technical changes
- Add context like "fixing issues with X" where relevant
- Keep entries concise but informative
6. Commit and push
git add -A && git commit -m "chore: release v{VERSION}
Co-Authored-By: Claude <[email protected]>"
git push -u origin release/v{VERSION}
7. Create PR
Provide the user with the PR creation URL or create it via gh pr create.
Important: Always pause after step 4 to discuss the changelog with the user before committing.
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.
- today First seen · 60 lines · 19 tokens per session scan A 660cfd53b079
release is a command published in the GitHub repository Joouis/agent-maestro (205 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 330 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
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
Walk the llmwiki release process step by step.