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 magnus919/agent-skills --skill release-engineeringgit clone --depth 1 https://github.com/magnus919/agent-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/magnus919/agent-skills/release-engineering)<a href="https://agentmods.dev/skills/magnus919/agent-skills/release-engineering"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/release-engineering.svg" alt="Measured on agentmods" 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.00158 | $0.03382 |
| Opus 5 | $0.00079 | $0.01691 |
| Sonnet 5 | $0.00032 | $0.00676 |
| Haiku 4.5 | $0.00016 | $0.00338 |
Grade A, and why
release-engineering 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 5d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Engineering
Senior-to-principal release engineering methodology: designing and operating the pipelines, processes, artifacts, gates, compliance evidence, and metrics that move software from commit to customer safely, predictably, and fast.
Ownership
| You own | You don't own |
|---|---|
| Release process design — branch strategy, process model, release cadence | Application feature implementation — route to backend-engineering / frontend-engineering |
| CD pipeline architecture — build-once promotion stages, gates, push-on-green | Production incident root-cause debugging — route to systematic-debugging |
| Progressive delivery — canaries, rings, percentage rollouts, feature flags | On-call and SLO operations — route to site-reliability-engineering |
| Versioning and artifacts — SemVer, conventional commits, changelogs, immutability, provenance | Security implementation and threat modeling — route to secure-software-engineering |
| Readiness and quality gates — release candidates, go/no-go, sign-off | Internal developer platform construction — route to platform-engineering |
| Rollback and recovery planning — runbooks, rehearsals, recovery targets | Data pipeline operations and schema migration engineering — route to data-engineering |
| Change governance and audit compliance — SOC 2 / SOX / PCI evidence chains | Spec authoring and SDD gate mechanics — route to spec-driven-development |
| DORA metrics — definitions, computation, thresholds | API contract design and versioning policy — route to api-design-and-evolution |
| Multi-team release coordination — trains, calendars, stabilization | Evidence collection and verdicts against explicit criteria — route to verification-methodology |
| Release operations — branch cuts, pipeline triage, emergency releases | Runtime monitoring and alerting — that's SRE |
What ships with it
38 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/deployment-strategy-matrix.md 3.6 KB
- assets/dora-metrics-reference.md 3.8 KB
- assets/release-toolchain-cheatsheet.md 5.4 KB
- assets/versioning-decision-table.md 3.4 KB
- evals/evals.json 9.2 KB
- pytest.ini 215 B
- README.md 3.8 KB
- references/cd-and-pipeline-stages.md 20 KB
- references/change-governance-and-compliance.md 23 KB
- references/feature-flag-lifecycle.md 20 KB
- references/metrics-and-dora.md 17 KB
- references/monorepo-polyrepo-release.md 20 KB
- references/progressive-delivery.md 21 KB
- references/readiness-and-quality-gates.md 20 KB
- references/release-operations-and-triage.md 25 KB
- references/release-process-models.md 20 KB
- references/role-and-career.md 22 KB
- references/rollback-and-recovery.md 24 KB
- references/skills-competency-model.md 17 KB
- references/supply-chain-security.md 18 KB
- references/toolchain-landscape.md 18 KB
- references/versioning-and-artifacts.md 20 KB
- scripts/changelog_check.py 15 KB runs code
- scripts/dora_metrics.py 18 KB runs code
- scripts/release_plan_scaffold.py 12 KB runs code
- scripts/semver_check.py 10 KB runs code
- scripts/version_bump.py 12 KB runs code
- templates/change-governance-record.md 4.7 KB
- templates/hotfix-emergency-release-plan.md 4.0 KB
- templates/release-notes.md 2.7 KB
- templates/release-plan.md 7.1 KB
- templates/release-readiness-checklist.md 4.8 KB
- templates/rollback-runbook.md 7.9 KB
- tests/test_changelog_check.py 14 KB runs code
- tests/test_dora_metrics.py 19 KB runs code
- tests/test_release_plan_scaffold.py 9.2 KB runs code
- tests/test_semver_check.py 8.3 KB runs code
- tests/test_version_bump.py 15 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.
- 5d ago First seen · 157 lines · 158 tokens per session scan A 92d2dce6cd59
release-engineering is a skill published in the GitHub repository magnus919/agent-skills (74 stars, last pushed yesterday), licensed MIT. It adds 158 tokens to every session and 3,382 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
ship
Enter the Ship phase of CocoBrew. Reads review.md approval, generates structured commit, creates semantic version tag, optionally creates PR via gh CLI, and records deployment details. Requires approved review.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
release-management
Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).