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 HigorAlves/orc --skill release-managementgit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/higoralves/orc/release-management)<a href="https://agentmods.dev/skills/higoralves/orc/release-management"><img src="https://agentmods.dev/badge/skills/higoralves/orc/release-management/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/higoralves/orc/release-management"><img src="https://agentmods.dev/badge/skills/higoralves/orc/release-management.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.00024 | $0.01423 |
| Opus 5.5 | $0.00010 | $0.00569 |
| Sonnet 5.5 | $0.00005 | $0.00285 |
| Haiku 4.5 | $0.00002 | $0.00142 |
Grade A, and why
release-management 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release management
Overview
A release is a mechanical consequence of the commit history, not a judgment call. Conventional commits since the last tag determine the bump; the same commits, grouped, become the changelog; an annotated tag plus a GitHub release publishes it. This skill defines the doctrine — /orc:release is the interactive command built on it.
Announce at start: "I'm using the release-management skill because this task cuts or prepares a release."
Hard rule — clean tree, green suite
Never release from a dirty tree or a red suite. Before anything else:
git status --porcelain # MUST be empty
<project test command> # MUST pass — run it, read the output
If either fails, stop. Do not stash, do not --no-verify, do not "tag now, fix later". A tag is a permanent public claim that this exact tree was releasable. There is no override flag for this rule.
Finding the last tag
git describe --tags --abbrev=0 # nearest tag on this branch
git tag --list --sort=-v:refname | head -5 # sanity-check against the full list
No tags at all → this is the first release: the commit range is the whole history, and the version is chosen (typically v0.1.0), not computed.
Semver decisioning
Collect commits since the last tag:
git log <last-tag>..HEAD --pretty='%H%x09%s%x09%b' --no-merges
Classify each subject against Conventional Commits, then take the highest bump any commit demands:
| Signal | Bump |
|---|---|
BREAKING CHANGE: in body/footer, or ! after type/scope (feat!:, fix(api)!:) |
major |
feat: / feat(scope): |
minor |
fix:, perf: |
patch |
docs:, refactor:, test:, build:, ci:, chore:, style:, revert: |
none on their own |
- Only none-bump commits since the last tag → surface it: there is nothing release-worthy. Releasing anyway (e.g. docs-only) is a deliberate user choice, defaulting to patch.
- Non-conventional subjects don't silently vanish: list them under an "Uncategorized" bucket and treat them as patch-level unless the diff clearly says otherwise.
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 Changed · +1 lines · -19 tokens per session c324c2f753df
- 1mo ago First seen · 116 lines · 43 tokens per session scan A 79c08304bcdb
release-management is a skill published in the GitHub repository HigorAlves/orc (7 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 1,423 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
fable-ship
Use when finishing a task — writing the final report or status, shipping a change, or handing off — to produce a calibrated done-claim and the docs that make the work reproducible by someone else.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.
talk-stage2-research
Performs git archaeology, changelog analysis, and builds a verified factual timeline by cross-referencing git history with source material. REX mode only (skipped automatically in Concept mode). Use when building a REX talk and you need verified commit metrics, release timelines, and contributor data from a git…