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 dungnotnull/hybrid-harness-chaos-process-prm --skill s28-release-managementgit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s28-release-management)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s28-release-management"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s28-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/dungnotnull/hybrid-harness-chaos-process-prm/s28-release-management"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s28-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.00101 | $0.02903 |
| Opus 5 | $0.00051 | $0.01452 |
| Sonnet 5 | $0.00020 | $0.00581 |
| Haiku 4.5 | $0.00010 | $0.00290 |
Grade A, and why
release-management scanned grade A with 1 finding 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 12d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
commits = subprocess.run( How it starts
The opening of the file, as written. The whole thing — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Management (s28)
Purpose
Orchestrate production releases with rigorous change management — ensuring every deployment has approval, verification, rollback readiness, stakeholder communication, and audit trail. Production is not a test environment; releases must be planned, not impulsive.
Prerequisites
- Pipeline YAML from s04
- Feature flags from s08 configured with kill switches
- Security scan from s11 passed (no HIGH/CRITICAL findings)
- Performance results from s13
- Resilience score from s26 (minimum 80 for production)
- Observability from s22 active and monitoring
Input Contract
| Input | Source | Required |
|---|---|---|
| All pipeline YAML (stages, approval gates) | s04 output | Yes |
| CV verification passed | s19 output | Yes |
| Resilience score ≥ 85 | s26 output | Yes |
| Security scan passed | s11 output | Yes |
| Performance baseline validated | s13 output | Yes |
| Feature flag states (what's staged vs live) | s08 output | Yes |
| Deployment window constraints | s02 taste (workflow), s22 (OPA) | Yes |
| Rollback plan | s04 (rollback steps), s10 (GitOps revert) | Yes |
Output Contract
| Output | Destination | Format |
|---|---|---|
| Release plan document | .commandcode/artifacts/releases/release-plan-<version>.md |
Markdown |
| Release notes (auto-generated) | .commandcode/artifacts/releases/release-notes-<version>.md |
Markdown |
| Change request ticket (Jira/ServiceNow) | External system | Ticket ID |
| Deployment calendar update | Team wiki / calendar | iCal/CSV |
| Stakeholder notification | Slack / Email | Message |
| Go/No-Go decision record | .commandcode/artifacts/releases/go-decision-<version>.md |
Markdown |
| Post-release validation | s19 (CV rerun), s26 (score update) | Trigger |
Release Lifecycle
PLAN → BUILD → VERIFY → APPROVE → DEPLOY → VALIDATE → COMMUNICATE → MONITOR
Week 1: Plan — Scope, schedule, stakeholders
Week 2: Build+Verify — CI/CD runs, tests pass, security gates pass
Day 0: Go/No-Go — Release readiness checklist
Day 1: Deploy — Canary/blue-green/rolling with CV
Hour 2: Validate — CV passes, SLOs maintained
Hour 2: Communicate — Release notes published, stakeholders notified
Day 1-7: Monitor — Error rates, latency, customer feedback
Day 7: Retro — What went well, what to improve
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.
- 12d ago First seen · 342 lines · 101 tokens per session scan A 7dab26971ffa
release-management is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 101 tokens to every session and 2,903 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.
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".