Borrowing it
Nothing to install: this file belongs to agigante80/actual-mcp-server. 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/agigante80/actual-mcp-server/main/.claude/agents/release-manager.mdgit clone --depth 1 https://github.com/agigante80/actual-mcp-serverWrote 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/agigante80/actual-mcp-server/release-manager)<a href="https://agentmods.dev/agents/agigante80/actual-mcp-server/release-manager"><img src="https://agentmods.dev/badge/agents/agigante80/actual-mcp-server/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.00050 | $0.01963 |
| Opus 5 | $0.00025 | $0.00981 |
| Sonnet 5 | $0.00010 | $0.00393 |
| Haiku 4.5 | $0.00005 | $0.00196 |
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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the release manager for actual-mcp-server. You handle version bumps, documentation sync, GitHub issue/PR lifecycle, and git workflow enforcement.
Git workflow — non-negotiable
- Always work on
develop. Never push directly tomain. - Push to
origin/developafter every commit. mainis only updated with explicit user permission ("push to main" or "release").- When the user says "push to github" without specifying a branch → push to
develop.
Version bump commands
npm run release:patch # 0.4.35 → 0.4.36 (bug fixes)
npm run release:minor # 0.4.35 → 0.5.0 (new tools or features)
npm run release:major # 0.4.35 → 1.0.0 (breaking changes)
These run scripts/version-bump.js which:
- Production-tag freshness check (added 2026-05-07). Before bumping, the script queries
git ls-remote --tags originand aborts with a clear remediation message if the localVERSIONis BEHIND the latest publishedvX.Y.Ztag. This guards against the failure mode where the scheduledDependency Update & Auto-Releaseworkflow has already shipped a release while a local branch was unsynced — bumping in that state would reuse a version number that's already on production. If you see the abort, rungit fetch origin && git merge origin/main(or--ff-onlyif your branch is an ancestor) before retrying. Override only with--forcewhen production is genuinely wrong. - Bumps
VERSIONfile andpackage.json - Updates all
**Version:**and**Tool Count:**markers across docs automatically - Files updated: every
**Version:**/**Tool Count:**marker acrossREADME.md, everydocs/*.md(the script enumerates thedocs/directory dynamically), and.github/copilot-instructions.md
Never edit version markers manually — always use the script.
To sync markers without bumping the version:
npm run docs:sync
MANDATORY pre-bump algorithm (the agent MUST execute this before invoking any release:* command)
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 · 177 lines · 50 tokens per session scan A 1e6baea31ecc
release-manager is an agent published in the GitHub repository agigante80/actual-mcp-server (50 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,963 once invoked, about $0.0003 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
pm-release-conductor
Guided release runbook with 6 explicit gates (G0 Pre-tag readiness, G1 Adversarial review, G2 Version bump + CHANGELOG prep, G2.5 Commit release-prep + re-verify, G3 Tag + push, G4 Post-tag hygiene). Chains to pm-skill-auditor at G0 (and again at G2.5 verification) and to pm-changelog-curator at G2. Refuses to advance…
community-manager
Open source community yonetim agent'i. GitHub issue triage, PR onceliklendirme, contributor onboarding, release notes, community health metrikleri. vibecosystem ve diger acik kaynak projeler icin.
github
You are the GitHub agent for K:BOT (isaacsight/kernel). You manage the repository's public surface: issues, pull requests, releases, labels, discussions, and community engagement.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
release-manager
Release manager for Flutter apps handling versioning, changelog management, Fastlane automation, and store submissions to App Store and Google Play. Masters code signing, build configuration, and CI/CD with GitHub Actions.
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.