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 niels-emmer/myace --skill release-engineeringgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/release-engineering)<a href="https://agentmods.dev/skills/niels-emmer/myace/release-engineering"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/release-engineering.svg" alt="Measured on agentmods" 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.00024 | $0.00544 |
| Opus 5 | $0.00012 | $0.00272 |
| Sonnet 5 | $0.00005 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00054 |
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 4d 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.
What it actually says
Purpose
A release is a contract with everyone downstream. Consistent versioning and a maintained changelog make it predictable; a defined hotfix path makes it reversible. This skill standardizes how versions are bumped, releases are cut, and urgent fixes are shipped — so a release is never a hand-rolled, one-off process.
When to use it
Any time you bump a version, cut a release, or ship an urgent fix to a released version.
Semantic versioning
Given MAJOR.MINOR.PATCH:
| Bump | When |
|---|---|
| MAJOR | Breaking API or behaviour change |
| MINOR | New feature, backward-compatible |
| PATCH | Bug fix, backward-compatible |
| PRE-RELEASE | MAJOR.MINOR.PATCH-<tag>.<number> (e.g. 1.0.0-beta.1) |
Pre-release precedence: alpha < beta < rc < stable.
Changelog
Maintain a changelog that records, per release, what was added, changed, fixed, and removed. Group by release version and date, and link each entry to its PR/issue where possible. Never rewrite history — append a new release section rather than editing old ones.
Cutting a release
- Confirm the target branch is green (CI passing, no open blockers).
- Bump the version per the table above.
- Update the changelog with the new release section.
- Tag the release commit (
v<MAJOR.MINOR.PATCH>). - Build/publish the release artifact from the tagged commit, not from a moving branch.
Hotfixes
- Branch from the release tag, not from main — the hotfix must contain only the fix, not unrelated changes that landed after the release.
- Apply the fix, bump PATCH, update the changelog.
- Release the hotfix from its own tag.
- Merge the fix back into main so it isn't lost.
Expected output
A versioned release with a maintained changelog, cut from a tagged commit, and a hotfix path that ships only the fix and merges it back.
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.
- 4d ago First seen · 52 lines · 24 tokens per session scan A 8e7d7e13e282
Release Engineering is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 544 once invoked, about $0.0001 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
cargo-release
PM-invocable protocol for Cargo publish and release operations in the trusty-tools Rust monorepo: semver rules, 10-step release sequence, macOS codesign safety, and cross-crate dependency ordering.
release-deploy
Release and deploy via GitHub tags and GitHub Actions (not every commit). Creates production releases from main and beta releases from staging using the GitHub CLI. Use when the user asks to release, ship, deploy, cut a version, tag a release, publish beta/production, create a GitHub Release, or bump a semver tag. On…
cut-release
Cut a clean release — bump versions across all files, update changelog, create GitHub release.
changelog
Generate or update a CHANGELOG.md in Keep a Changelog format from real git history. Use when cutting a release, tagging a version, or asked "what changed since…".
release-manager
A release-management tool for calculating semantic versions, generating changelogs and release notes, creating tags, and preparing releases. Semantic versioning uses version numbers to describe the scale of changes.
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.