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 ashermahonin/agentic-skills --skill release-managementgit clone --depth 1 https://github.com/ashermahonin/agentic-skillsWrote 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/ashermahonin/agentic-skills/release-management)<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/release-management"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/release-management/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/ashermahonin/agentic-skills/release-management"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/release-management.svg" alt="Reviewed on agentmods" width="80" 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.00067 | $0.00884 |
| Opus 5 | $0.00034 | $0.00442 |
| Sonnet 5 | $0.00013 | $0.00177 |
| Haiku 4.5 | $0.00007 | $0.00088 |
Grade A, and why
release-management 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 9d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Management
Purpose
Turn verified changes into a controlled release. Collect the checks that apply to the product, name the approver and blockers, define rollout and rollback, and verify the system after deployment.
Operational context
- Read
references/release-checklist.md. - Pull verdicts from
qa-eval,security-owasp-*,cve-zero-day-scanner,accessibility-audit,i18n-localization,pr-review,tdd-workflow. - Pull deployment surface from
devops-router/cicd-automation/cloud-operations/kubernetes-operations. - Use Context7 MCP for current store policies, certification checklists, version-numbering conventions, signing requirements, and registry submission rules.
Safe change sequence
- Versioning. Decide on the version bump (semver, calver, marketing version + build number). Lock the version string.
- Build provenance. Attach SLSA-style provenance: source commit, build steps, artifact hash, signing key, SBOM.
- Release notes. Two flavors: internal (full changelog, risks, rollback) and user-facing (highlights, fixes, known issues), localized per locale via
i18n-localization. - Store / registry submission. Per channel: build artifact, signing, metadata, screenshots, age rating, privacy disclosure, content rating, encryption export compliance, store-specific reviews.
- Staged rollout. Define rollout stages: canary % → broader % → full, with hold criteria per stage based on error rate, crash rate, p95 latency, business KPI.
- Go/no-go report. Single page: every gate's verdict, named approver per gate, residual risks, rollback path, on-call rotation.
- Post-release verification. First N minutes / hours: watch dashboards from
observability-operations, telemetry, store reviews, support tickets. Promote or rollback based on hold criteria. - Retro hook. After release stabilizes, hand off to
documentation-graph-curatorto log decisions, anomalies, and lessons.
Safety rules
What ships with it
2 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.
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.
- 9d ago First seen · 63 lines · 67 tokens per session scan A 221e95e0fb06
release-management is a skill published in the GitHub repository ashermahonin/agentic-skills (10 stars, last pushed 15d ago), licensed MIT. It adds 67 tokens to every session and 884 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.