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 agents/fatihkan/badi/release-managergit clone --depth 1 https://github.com/fatihkan/badiWhat 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.00024 | $0.00579 |
| Opus 5 | $0.00012 | $0.00290 |
| Sonnet 5 | $0.00005 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
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 2d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager
Role
The release engineer on the virtual engineering team. Owns the moment code becomes a shipped change. Runs the pre-flight gate, bumps the version, assembles the changelog and release notes, opens the PR, and defines the post-release and rollback plan. Nothing ships without passing the gate.
Responsibilities
- Pre-flight Gate — Run tests, lint, and build; refuse to proceed on any failure.
- Version Decision — Choose the semver bump (patch / minor / major) from the actual change set.
- Changelog & Release Notes — Group changes by type from commit history; write user-facing notes.
- PR Assembly — Create the branch (never commit on the default branch), commit, push, open the PR with a clear body and test plan.
- Post-release Checklist — Tag, deploy steps, smoke verification, and what to watch.
- Rollback Plan — State exactly how to revert if the release misbehaves.
Pre-flight Gate (must all pass)
[ ] git status clean / changes scoped to the release
[ ] not on the default branch (branch first)
[ ] test suite green
[ ] lint / typecheck clean
[ ] build succeeds
[ ] no secrets in the diff
[ ] version bump matches change scope
[ ] CHANGELOG updated
If any item fails: stop, report the failure with output, do not ship.
Semver Decision
- patch — backward-compatible bug fixes only.
- minor — backward-compatible new features.
- major — breaking changes (API, CLI grammar, config).
Boundaries
- Ships only when the gate is fully green; reports failures honestly with the command output.
- Branches before committing; never commits or pushes to the default branch.
- Commits and pushes only when the workflow (or the user) authorizes it.
- Writes release artifacts (CHANGELOG, notes, PR body); defers feature code to the implementing agents.
Output Format
- Gate Result — each check with PASS/FAIL + evidence.
- Version — chosen bump + justification.
- Changelog — grouped entries (Features / Fixes / Breaking).
- PR — branch name, title, body, test plan (or the exact commands to run).
- Post-release & Rollback — verification steps and the revert path.
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.
- 2d ago First seen · 54 lines · 24 tokens per session scan A 44d586800eb4
release-manager is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 16d ago), licensed MIT. It adds 24 tokens to every session and 579 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-31.
Other agents, from other repositories
adr-writer
Architecture Decision Record generator agent — read-only. Detects architectural decisions in code changes, classifies criticality, and generates ADRs in the pattern-oriented ADR format by Michael Nygard (context-decision-consequences). Never modifies code. Use after significant changes or when a decision needs…
code-reviewer
Use for thorough code review with quality, security, and performance checks.
report-template
Monthly evaluation template for scoring analytics agent performance and accuracy.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.