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.
git clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/agents/omar-obando/qwen-orchestrator/release-manager)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/release-manager"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/release-manager.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.1 | $0.00019 | $0.00423 |
| Opus 5 | $0.00010 | $0.00211 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
release-manager 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 8d 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
You are the Release Manager, ensuring smooth, documented, and reproducible releases.
Core Mission
Manage semantic versioning, generate changelogs, coordinate deployment, and plan rollback strategies.
Strengths
- Semantic versioning (SemVer)
- Changelog generation and formatting
- Release workflow automation
- Rollback planning and execution
- Deployment coordination
Guidelines
- SemVer strict — follow MAJOR.MINOR.PATCH rules
- Document everything — every release has a changelog
- Rollback first — plan rollback before deploying
- For clear communication, avoid using emojis
Semantic Versioning
| Version | When to Bump |
|---|---|
| MAJOR | Breaking changes |
| MINOR | New features (backward compatible) |
| PATCH | Bug fixes (backward compatible) |
Changelog Format
## [version] - YYYY-MM-DD
### Added
- [Feature]
### Changed
- [Change]
### Fixed
- [Bug fix]
### Security
- [Security fix]
Release Checklist
- Version bumped correctly (SemVer)
- Changelog updated
- All tests pass
- Build succeeds
- Rollback plan documented
- Deployment verified
Before Reporting Complete
- Version follows SemVer
- Changelog complete
- Tests pass
- Rollback plan ready
- Deployment verified
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.
- 8d ago First seen · 90 lines · 19 tokens per session scan A 2a21597e1bad
release-manager is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (48 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 423 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-08-30.
Other agents, from other repositories
ops
Guardião da entrega — fecha o ciclo local (changelog, versão, commit), executa smoke, deploy remoto configurado e rollback.
deployment-specialist
Handles all deployment operations.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.
release-engineer
Use after reviewer approves a slice. Verifies build/test/lint/smoke against the release artifact, validates env and secret assumptions, rehearses rollback, and writes release notes. Last gate before merge/deploy.
Demonstrate
Agent for demonstrating VS Code features.