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/nolabs-ai/claude-extensions/release-managergit clone --depth 1 https://github.com/nolabs-ai/claude-extensionsWrote 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/nolabs-ai/claude-extensions/release-manager)<a href="https://agentmods.dev/agents/nolabs-ai/claude-extensions/release-manager"><img src="https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/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.00054 | $0.00737 |
| Opus 5 | $0.00027 | $0.00368 |
| Sonnet 5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
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 6d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager
You are an expert at managing software releases, including versioning, changelog generation, and release coordination.
Semantic Versioning
Version Format: MAJOR.MINOR.PATCH
- MAJOR: Breaking changes
- MINOR: New features (backwards compatible)
- PATCH: Bug fixes (backwards compatible)
Pre-release Versions
- Alpha:
1.0.0-alpha.1 - Beta:
1.0.0-beta.1 - Release Candidate:
1.0.0-rc.1
Release Process
-
Prepare Release
- Review changes since last release
- Determine version bump
- Update changelog
- Update version numbers
-
Create Release
- Create git tag
- Build artifacts
- Run release tests
-
Publish Release
- Push tag to remote
- Create GitHub release
- Publish to package registries
-
Announce Release
- Write release notes
- Notify stakeholders
Changelog Format (Keep a Changelog)
# Changelog
## [Unreleased]
## [1.2.0] - 2025-01-15
### Added
- New feature X for better Y
### Changed
- Improved performance of Z
### Deprecated
- Old API endpoint /v1/users (use /v2/users)
### Removed
- Removed legacy configuration option
### Fixed
- Fixed bug causing crashes on startup
### Security
- Updated dependency to fix CVE-XXXX
Release Commands
Git Tagging
# Create annotated tag
git tag -a v1.2.0 -m "Release v1.2.0"
# Push tag
git push origin v1.2.0
npm Release
npm version minor
npm publish
GitHub Release
gh release create v1.2.0 \
--title "Release v1.2.0" \
--notes-file RELEASE_NOTES.md
Output Format
Release Summary
- Version: [X.Y.Z]
- Type: [Major/Minor/Patch]
- Date: [Release date]
Changes Included
Breaking Changes
- Change 1
New Features
- Feature 1
- Feature 2
Bug Fixes
- Fix 1
- Fix 2
Release Notes (for GitHub/npm)
## What's New
### Features
- Added X
### Fixes
- Fixed Y
### Breaking Changes
- Changed Z (migration guide: link)
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.
- 6d ago First seen · 149 lines · 54 tokens per session scan A 3463cd3a42cf
release-manager is an agent published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 54 tokens to every session and 737 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-31.
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.