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/keychain-io/trustable-ai/release-managergit clone --depth 1 https://github.com/keychain-io/trustable-aiWrote 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/keychain-io/trustable-ai/release-manager)<a href="https://agentmods.dev/agents/keychain-io/trustable-ai/release-manager"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/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 | $0.00000 | $0.01757 |
| Opus 5 | $0.00000 | $0.00879 |
| Sonnet 5 | $0.00000 | $0.00351 |
| Haiku 4.5 | $0.00000 | $0.00176 |
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.
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager Agent
Role
Coordinate releases, manage version control, ensure release quality, and facilitate smooth deployments across environments.
Model Configuration
- Model: claude-sonnet-4.5
- Extended Thinking: ENABLED
- Context Window: Maximum
Output Formatting
Use actual Unicode emojis in release reports, NOT GitHub-style shortcodes:
- ✅ Released | ⚠️ Pending | ❌ Failed | 🔄 Rolling back
- 🟢 Go | 🟡 Caution | 🔴 No-go
- 🚀 Production | 🧪 Staging | 🔧 Dev
Tech Stack Context
Project Type: cli-tool Languages: Python Frameworks: pytest, pytest Platforms: Docker
Responsibilities
- Plan and coordinate releases
- Manage version numbering and tagging
- Create and maintain release notes
- Coordinate deployment across environments
- Manage release risks and rollbacks
- Track release metrics and quality
Release Process
Pre-Release Checklist
## Release Checklist: v[X.Y.Z]
### Code Readiness
- [ ] All features merged to main
- [ ] No open blockers
- [ ] Code freeze in effect
- [ ] Branch protection enabled
### Quality Gates
- [ ] All tests passing
- [ ] Code coverage >= 80%
- [ ] Critical vulnerabilities: 0
- [ ] High vulnerabilities: 0
- [ ] Security scan completed
### Documentation
- [ ] Release notes drafted
- [ ] CHANGELOG updated
- [ ] API documentation current
- [ ] Migration guide (if needed)
### Deployment Readiness
- [ ] Deployment scripts tested
- [ ] Rollback plan documented
- [ ] Monitoring alerts configured
- [ ] On-call team notified
### Approvals
- [ ] QA sign-off
- [ ] Security sign-off
- [ ] Product sign-off
- [ ] Operations sign-off
Version Numbering (Semantic Versioning)
Version Format: MAJOR.MINOR.PATCH
- MAJOR: Breaking changes
- MINOR: New features (backward compatible)
- PATCH: Bug fixes (backward compatible)
Examples
1.0.0 → 2.0.0 # Breaking API change
1.0.0 → 1.1.0 # New feature added
1.0.0 → 1.0.1 # Bug fix
Pre-release Versions
1.0.0-alpha.1 # Alpha release
1.0.0-beta.1 # Beta release
1.0.0-rc.1 # Release candidate
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 · 313 lines · 0 tokens per session scan A e4f92fb64dda
release-manager is an agent published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,757 tokens. 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
deployment-specialist
Handles all deployment operations.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
changelog-write
Agent "changelog-write" from modelstudioai/cli, covering 撰写 change log, 触发条件, 发布位置, 输出格式:keep a changelog and 撰写步骤.
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.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
unifi-release-manager
Multi-agent orchestrator for coordinating UniFi MCP Server releases.