Borrowing it
Nothing to install: this file belongs to dixus/claudeframework. 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/dixus/claudeframework/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/dixus/claudeframeworkWrote 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/dixus/claudeframework/release)<a href="https://agentmods.dev/skills/dixus/claudeframework/release"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/release/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/dixus/claudeframework/release"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/release.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.00046 | $0.02202 |
| Opus 5.5 | $0.00018 | $0.00881 |
| Sonnet 5.5 | $0.00009 | $0.00440 |
| Haiku 4.5 | $0.00005 | $0.00220 |
Grade A, and why
release 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.
Cut a quarterly release. Replaces a hand-rolled release workflow (which tends to drift — tags get forgotten, notes get written late) with a deterministic, reproducible cut.
What this skill does:
- Validate state (clean tree, on the main branch, up to date)
- Cut a release branch
Q<N>-Release-<YYYY>from the main branch - Run the
/release-notesskill to generatereleases/<quarter>.md - Commit the release-notes file on the new branch
- Tag the cut commit (default: same name as the branch)
- Show a summary, gate before push
- Push branch + tag on confirmation
What this skill does NOT do:
- Trigger the project's build/release pipelines. If the project has pipelines that must be started manually for a release branch, the final report lists them as next steps. Automating that trigger is a project-specific follow-up (credentials, pipeline ids, API choice).
- Handle hotfix releases. Those go through
<ticket>-on-<release-branch>branches as documented in.claude/rules/branch-management.md(if the project defines one) and merge into the release branch, not the main branch.
Throughout, <main> is the repo's default branch (main or master — check git symbolic-ref --short refs/remotes/origin/HEAD). If branch-management.md defines a different release-branch convention, follow that instead of the Q<N>-Release-<YYYY> default.
Step 0 — Parse arguments
<quarter> is required. Accepted formats (case-insensitive):
2026-Q2(preferred — sortable)Q2-2026Q2 2026
Extract:
Q(integer, 1–4) — abort if invalidYYYY(4-digit year) — abort if not in(current year - 1)..(current year + 1)- Compute:
branch_name = Q<Q>-Release-<YYYY>quarter_id = <YYYY>-Q<Q>(sortable, used forreleases/<quarter_id>.md)default_tag = <branch_name>(override with--tag)
Optional flags:
--dry-run— run validation + computation + release-notes preview, but do not create branch/tag/commit/push--tag <name>— override the default tag name--no-tag— skip tag creation entirely--since <ref>— passed through to/release-notesto override the range start (default: auto-detect from latestreleases/*.md)
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 · 46 tokens per session scan A c04785106829
release is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 2,202 once invoked, about $0.0002 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-16.
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.
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.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.