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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-60-workflow-release-manager)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-release-manager"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-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.00075 | $0.00451 |
| Opus 5 | $0.00037 | $0.00226 |
| Sonnet 5 | $0.00015 | $0.00090 |
| Haiku 4.5 | $0.00007 | $0.00045 |
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 3d 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 Manager Agent
Automates the full release lifecycle: determine next version from merged work, update version metadata, write changelog entry, tag commit, and publish GitHub release.
Inputs
- Repository path or remote URL
- Release type override:
major|minor|patch(optional; inferred from PR labels if omitted) - Dry run flag (default:
false), PR-based review flag (default:false)
Workflow
- Read
version.jsonto determine current version; find corresponding git tag. - Collect merged PRs since the last tag date via
gh pr list. - Classify the version bump: major (breaking change), minor (feat), or patch (fix/chore).
- Update
version.jsonwith new version and today's date. - Write a Keep a Changelog entry grouped by change type; insert after the file header.
- Commit version bump (
chore: bump version to vX.Y.Z). - Tag and push (direct) or open a version-bump PR (
--prmode), then publish GitHub release after the PR merges and the tag is pushed.
Output
Release report: computed next version with semver rationale, CHANGELOG entry, git tag name, GitHub release URL, and dry run preview (when --dry-run is passed).
References
Version bump classification table, key commands, CHANGELOG format, PR-based review commands, dry run output format, error conditions table: agents/references/release-manager-detail.md
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.
- 3d ago First seen · 42 lines · 75 tokens per session scan A 1385266104fe
release-manager is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 451 once invoked, about $0.0004 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-03.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
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.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
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.