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 the-open-agent/oss-skills --skill release-engineeringgit clone --depth 1 https://github.com/the-open-agent/oss-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/the-open-agent/oss-skills/release-engineering)<a href="https://agentmods.dev/skills/the-open-agent/oss-skills/release-engineering"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/release-engineering/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/the-open-agent/oss-skills/release-engineering"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/release-engineering.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.00108 | $0.02366 |
| Opus 5.5 | $0.00043 | $0.00946 |
| Sonnet 5.5 | $0.00022 | $0.00473 |
| Haiku 4.5 | $0.00011 | $0.00237 |
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 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Engineering
A release is a promise. Semver is the notation for that promise, and users treat it literally — a breaking change in a patch release breaks builds at 3 a.m. for people who did nothing wrong.
Semver, decided correctly
MAJOR.MINOR.PATCH — increment MAJOR for incompatible changes, MINOR for
backward-compatible additions, PATCH for backward-compatible fixes.
The judgment calls, resolved:
| Change | Bump | Note |
|---|---|---|
| Add an optional parameter | minor | |
| Add a required parameter | major | |
| Add a new export | minor | |
| Remove or rename any export | major | Deprecate first (api-design) |
| Change a default value | major | Behavior changes silently — the worst kind |
| Fix a bug users may depend on | major in practice | Hyrum's Law; judge by blast radius |
| Add a new error type | minor | Unless callers must handle it exhaustively |
| Change an error message | patch | Unless documented as stable |
| Change an error type | major | |
| Tighten input validation | major | Previously-working input now fails |
| Loosen validation | minor | |
| Raise minimum runtime version | major | Node 18→20, Python 3.9→3.10 |
| Add a required peer dependency | major | |
| Bump a dependency's major | major if its types are in your public API, else minor | |
| Performance improvement | patch/minor | major if a complexity guarantee changes |
| Docs, tests, CI | none | No release needed |
| Change output ordering | major if previously stable | Someone parses it |
0.x is not an exemption from thinking. Convention: 0.MINOR.PATCH where minor
carries breaking changes. But once real users exist, communicate breaks regardless of
what the version number technically permits.
1.0 means "the API is stable and I will honor semver." Ship it once that is true.
Sitting at 0.x for years while enterprises depend on you is worse than an honest 1.0 —
0.x is read by procurement as "not production ready", and by dependency tooling as
"pin exactly".
What ships with it
1 file 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.
- 1mo ago First seen · 208 lines · 108 tokens per session scan A f43313269cb8
release-engineering is a skill published in the GitHub repository the-open-agent/oss-skills (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 108 tokens to every session and 2,366 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-pages-publish
Publish or update a static site (gh-pages) on GitHub Pages via GitHub Actions in any repo: text or pre-built HTML in, workflow set up, live URL verified. Don't use for CI test pipelines, framework/SSG builds, or Netlify/Vercel hosting.
github-cli
A command-line tool connection for GitHub tasks that built-in tools do not cover. It uses GitHub's command-line program to work with issues, pull requests, releases, workflows, searches, and the GitHub API.
hyperframes-pr-to-video
Turn a GitHub pull request into a changelog, feature-reveal, fix, or refactor explainer video using HyperFrames. Use when the user provides a PR URL, owner/repo#N ref, or says 'this PR'. Reads diff via gh CLI, visualizes code changes as animated diffs with narration. Teaches diff parsing, change visualization, and…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
deploy-pipeline-runbook
Use when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt state in a downstream system.