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 skills add sampleXbro/agentsmesh --skill release-managergit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/skills/samplexbro/agentsmesh/release-manager)<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/release-manager"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/release-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/release-manager"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/release-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00005 | $0.03656 |
| Opus 5.5 | $0.00002 | $0.01462 |
| Sonnet 5.5 | $0.00001 | $0.00731 |
| Haiku 4.5 | $0.00001 | $0.00366 |
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 1mo 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 — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Release Manager
Tier: POWERFUL
Category: Engineering
Domain: Software Release Management & DevOps
Overview
The Release Manager skill provides comprehensive tools and knowledge for managing software releases end-to-end. From parsing conventional commits to generating changelogs, determining version bumps, and orchestrating release processes, this skill ensures reliable, predictable, and well-documented software releases.
Core Capabilities
- Automated Changelog Generation from git history using conventional commits
- Semantic Version Bumping based on commit analysis and breaking changes
- Release Readiness Assessment with comprehensive checklists and validation
- Release Planning & Coordination with stakeholder communication templates
- Rollback Planning with automated recovery procedures
- Hotfix Management for emergency releases
- Feature Flag Integration for progressive rollouts
Key Components
Scripts
- changelog_generator.py - Parses git logs and generates structured changelogs
- version_bumper.py - Determines correct version bumps from conventional commits
- release_planner.py - Assesses release readiness and generates coordination plans
Documentation
- Comprehensive release management methodology
- Conventional commits specification and examples
- Release workflow comparisons (Git Flow, Trunk-based, GitHub Flow)
- Hotfix procedures and emergency response protocols
Release Management Methodology
Semantic Versioning (SemVer)
Semantic Versioning follows the MAJOR.MINOR.PATCH format where:
- MAJOR version when you make incompatible API changes
- MINOR version when you add functionality in a backwards compatible manner
- PATCH version when you make backwards compatible bug fixes
Pre-release Versions
Pre-release versions are denoted by appending a hyphen and identifiers:
1.0.0-alpha.1- Alpha releases for early testing1.0.0-beta.2- Beta releases for wider testing1.0.0-rc.1- Release candidates for final validation
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/sample_commits.json 7.3 KB
- assets/sample_git_log_full.txt 5.9 KB
- assets/sample_git_log.txt 2.0 KB
- assets/sample_release_plan.json 8.5 KB
- changelog_generator.py 19 KB runs code
- expected_outputs/changelog_example.md 1.3 KB
- expected_outputs/release_readiness_example.txt 927 B
- expected_outputs/version_bump_example.txt 742 B
- README.md 14 KB
- references/conventional-commits-guide.md 9.1 KB
- references/hotfix-procedures.md 15 KB
- references/release-workflow-comparison.md 13 KB
- release_planner.py 39 KB runs code
- version_bumper.py 23 KB runs code
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.
- 1mo ago First seen · 492 lines · 5 tokens per session scan A bef37ef3b482
release-manager is a skill published in the GitHub repository sampleXbro/agentsmesh (25 stars, last pushed 22d ago), licensed MIT. It adds 5 tokens to every session and 3,656 once invoked, about $0.0000 per session on Opus 5.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 skills, from other repositories
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
release-notes
Drafts concise release notes from merged pull requests and conventional commits. Use when the user asks for a changelog, release notes, or a GitHub release body.
fork-and-publish-skill
Customizes an installed agent skill and ships it back upstream or as a versioned fork using qvr's edit/publish authoring loop. Use when a user wants to modify, customize, fork, release, or publish a qvr skill — e.g. "edit this skill", "publish my changes", "fork a skill to my own repo", "cut a v1.0.0 release of a…
changelog
Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.
deploy-check
Confirm build outputs, environment variables, release notes, and rollback steps before touching deployment configuration.