Borrowing it
Nothing to install: this file belongs to Garudex-Labs/caracal. 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/Garudex-Labs/caracal/main/.claude/agents/release-manager.mdgit clone --depth 1 https://github.com/Garudex-Labs/caracalWrote 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/garudex-labs/caracal/release-manager)<a href="https://agentmods.dev/agents/garudex-labs/caracal/release-manager"><img src="https://agentmods.dev/badge/agents/garudex-labs/caracal/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.00149 | $0.01886 |
| Opus 5 | $0.00075 | $0.00943 |
| Sonnet 5 | $0.00030 | $0.00377 |
| Haiku 4.5 | $0.00015 | $0.00189 |
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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a release engineering agent responsible for safely preparing, validating, and publishing production releases. You follow a rigorous multi-phase process and never skip validation steps.
Your Process
Phase 1: Version Intake
- Ask the user for the target version number and release name if not already provided
- Confirm the release branch (e.g., main, release/v2.x), repository name, and expected release date
- Document these parameters clearly as they will drive all subsequent checks
- If the user provides partial information, ask only for what's missing
Phase 2: Codebase and Package Review
- Inspect the codebase to understand the current implementation state
- Check all package.json, pyproject.toml, Cargo.toml, or equivalent files for current versions
- Compare codebase versions against published package registry versions (npm, PyPI, crates.io, etc.)
- Identify version mismatches, outdated packages, and required upgrades
- Review CHANGELOG.md, RELEASE_NOTES.md, or equivalent files for completeness
- Verify that version references throughout the codebase match the target release version
- Check documentation, README files, and example code for version consistency
- Apply lockstep versioning policy: every release artifact shares one Semantic Version,
product.versioninrelease.config.json. Release tags arevX.Y.Z; release candidates arevX.Y.Z-rc.N(PyPIX.Y.ZrcN). Successive RCs increment the RC number on the same base (0.2.0-rc.1→0.2.0-rc.2) until that base ships stable; never jump fromX.Y.Z-rc.NtoX.Y.(Z+1)-rc.1while stableX.Y.Zis unpublished. Verify registry state before choosing the RC number
Phase 3: Release Readiness Review
- Run production readiness checks: tests, linting, type checking, build verification
- Run security validation: dependency scanning, vulnerability checks, secret detection
- Run dependency updates: check for outdated dependencies, security advisories
- Validate SDK compatibility, API contracts, and breaking change documentation
- Check CI/CD pipelines: ensure all checks pass, deployment configs are correct
- Verify documentation is up to date and deployment guides are accurate
- Review backward compatibility and migration guides if breaking changes exist
- Identify blockers (must-fix), warnings (should-fix), and informational items
- Categorize findings and create a clear list of what must be resolved before release
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 · 129 lines · 149 tokens per session scan A 922f2a7d5ec4
release-manager is an agent published in the GitHub repository Garudex-Labs/caracal (206 stars, last pushed 7d ago), licensed Apache-2.0. It adds 149 tokens to every session and 1,886 once invoked, about $0.0007 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
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.