Borrowing it
Nothing to install: this file belongs to umbraco/Umbraco.Automate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/umbraco/Umbraco.Automate/v18/dev/.claude/skills/ops-release/SKILL.mdgit clone --depth 1 https://github.com/umbraco/Umbraco.AutomateWrote 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/umbraco/umbraco.automate/ops-release)<a href="https://agentmods.dev/skills/umbraco/umbraco.automate/ops-release"><img src="https://agentmods.dev/badge/skills/umbraco/umbraco.automate/ops-release.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.00084 | $0.03372 |
| Opus 5 | $0.00042 | $0.01686 |
| Sonnet 5 | $0.00017 | $0.00674 |
| Haiku 4.5 | $0.00008 | $0.00337 |
Grade A, and why
ops-release 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl` here. How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ops-release
Turn a release trigger into a shipped release for this repo: plan it, cut it, publish it, then put the line's branches back in step.
Visibility: service. A framework loop may command it.
Invocation
ops-release <action> '<context-json>'
Two positional arguments. context is a single JSON object encoded as a string; an
absent context is {}, not an error. Reject any action not listed below — never
guess at one, and never silently succeed.
| Action | What it must do |
|---|---|
plan |
Turn the trigger into release facts: which line, which version, and which units of work the release contains. Reads only; opens nothing. |
cut |
Branch, bump the version files, write the changelog, and open the release PR. Idempotent: re-running MUST return the existing release PR, never open a second. |
publish |
Realize the release once its PR has landed: tag the commit, push the artifacts to their feed, and publish the release notes. MUST leave nothing half-published on failure. |
sync |
Put the line's branches back in step after a release, so the next change starts from what actually shipped. The step manual releases most often forget. |
Repo facts every action depends on
Two version schemes, and they are not the same thing.
| Scheme | Looks like | Where it lives | What it names |
|---|---|---|---|
| Release number | 2026.07.4 |
the release branch and the GitHub release | one shipping event, date-based |
| Product version | 18.1.0 |
<Product>/version.json (Nerdbank.GitVersioning) |
one package, semver |
So one release ships several products, each at its own semver, under one date-based number. The
version in the trigger issue title (release 2026.08.1) is the release number.
Naming, all of which already exists and must not drift:
- Release branch:
<line>/release/<release-number>— e.g.v18/release/2026.07.3 - Release PR title:
chore(release): Prepare release <release-number> (<line>) - Per-product tag:
<Product>@<semver>— e.g.[email protected] - Release tag:
<release-number>— e.g.2026.07.4 - GitHub release title:
Release <release-number>
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.
- 8d ago First seen · 288 lines · 84 tokens per session scan A 41b83b492e50
ops-release is a skill published in the GitHub repository umbraco/Umbraco.Automate (5 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 3,372 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
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".
updater_guide
Guidance for checking for and installing Row-Bot updates.