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 wyattowalsh/agents --skill release-pipeline-architectgit clone --depth 1 https://github.com/wyattowalsh/agentsWrote 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/wyattowalsh/agents/release-pipeline-architect)<a href="https://agentmods.dev/skills/wyattowalsh/agents/release-pipeline-architect"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/release-pipeline-architect/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/wyattowalsh/agents/release-pipeline-architect"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/release-pipeline-architect.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.00036 | $0.01742 |
| Opus 5.5 | $0.00014 | $0.00697 |
| Sonnet 5.5 | $0.00007 | $0.00348 |
| Haiku 4.5 | $0.00004 | $0.00174 |
Grade A, and why
release-pipeline-architect 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Pipeline Architect
Design release pipelines that move one immutable artifact through test, staging, and production with clear gates, rollout strategy, and rollback procedure.
Scope: Release orchestration after code is ready. NOT for infrastructure provisioning (infrastructure-coder), generic CI job optimization (devops-engineer), or release-note writing (changelog-writer).
Canonical Vocabulary
| Term | Definition |
|---|---|
| release candidate | A versioned build proposed for promotion |
| artifact | The immutable build output promoted across environments |
| promotion | Moving the same artifact to the next environment |
| gate | A manual or automated approval checkpoint |
| provenance | Evidence tying an artifact to source commit, build, and checks |
| rollout | The production exposure strategy: all-at-once, canary, or phased |
| rollback point | The last known-good release that can be restored safely |
| freeze window | A period where changes are limited to release-critical work |
| hotfix lane | A minimal path for urgent production repairs |
Dispatch
| $ARGUMENTS | Mode |
|---|---|
design <requirements> |
Design a release pipeline and operating model |
review <pipeline or runbook> |
Audit an existing release flow |
cutover <release> |
Plan the release-day sequence and handoffs |
hotfix <incident> |
Design an emergency release lane |
checklist <release type> |
Produce a release readiness checklist |
| Natural language about release workflows | Auto-detect the closest mode |
| Empty | Show the mode menu with examples |
Mode Menu
| # | Mode | Example |
|---|---|---|
| 1 | Design | design weekly SaaS release with staging and canary prod |
| 2 | Review | review .github/workflows/release.yml |
| 3 | Cutover | cutover v2.8.0 |
| 4 | Hotfix | hotfix rollback path for broken payments deploy |
| 5 | Checklist | checklist mobile app store release |
What ships with it
13 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.
- evals/evals.json 7.2 KB
- references/failure-modes.md 2.4 KB
- references/provenance-evidence-checklist.md 1.5 KB
- references/rollout-decision-matrix.md 2.4 KB
- references/runbook-templates.md 1.6 KB
- scripts/asset_toolkit/__init__.py 303 B runs code
- scripts/asset_toolkit/_shared.py 5.6 KB runs code
- scripts/asset_toolkit/common.py 3.0 KB runs code
- scripts/asset_toolkit/package.py 43 KB runs code
- scripts/asset_toolkit/validate_evals.py 11 KB runs code
- scripts/asset_toolkit/validate_hooks.py 13 KB runs code
- scripts/asset_toolkit/validate_skill.py 3.6 KB runs code
- scripts/check.py 2.2 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 · 150 lines · 36 tokens per session scan A 69f47b15f9aa
release-pipeline-architect is a skill published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,742 once invoked, about $0.0001 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-09-03.
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.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
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.