release

release is a skill for Claude Code, Codex from phodal/routa. It costs 38 tokens per session (511 once invoked), scanned A, original, MIT.

A Routa release-preparation workflow that synchronizes versions and creates release notes, changelogs, and a summary file.

In plain words
What is it for?
Use it to prepare or dry-run a Routa release, generate release documentation, or publish a confirmed version with the repository's scripts.
Why use it?
It gathers the files needed for a release in a repeatable process and can stop before any commit, tag, or push needs human approval.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/phodal/routa/release
Any agent
npx skills add phodal/routa --skill release
Clone the repo
git clone --depth 1 https://github.com/phodal/routa

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/phodal/routa/release.svg)](https://agentmods.dev/skills/phodal/routa/release)
Your own site
<a href="https://agentmods.dev/skills/phodal/routa/release"><img src="https://agentmods.dev/badge/skills/phodal/routa/release.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 511 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00511
Opus 5 $0.00019 $0.00255
Sonnet 5 $0.00008 $0.00102
Haiku 4.5 $0.00004 $0.00051

Measured 4d ago against content hash 0e5545c82250, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.agents/skills/release/SKILL.md · 56 lines

What it actually says

Prepare Routa releases with the existing repo scripts. Keep the workflow deterministic until human confirmation is needed for commit, tag, or push.

When to use

  • The user asks to release Routa, publish a version, prepare release notes, or generate a release blog post.
  • The task needs synchronized version bumps plus docs/releases/ artifacts.

Workflow

  1. Confirm the target version and whether the user wants a dry run or an actual publish.
  2. If a release summary already exists, pass it with --summary-file. If the user wants AI-generated summary copy, add --ai and optionally --ai-provider <name>.
  3. Run the helper:
node scripts/release/prepare-release-artifacts.mjs <version>
node scripts/release/prepare-release-artifacts.mjs <version> --from <previous-tag> --ai --ai-provider claude
  1. Review the generated files:
    • docs/releases/v<version>-release-notes.md
    • docs/releases/v<version>-changelog.md
    • dist/release/changelog-summary-prompt.json
  2. If the user only wants preparation, stop after review and validation.
  3. If the user wants to publish, continue with either:
./scripts/release/publish.sh <version>

or the manual flow documented in docs/release-guide.md.

Guardrails

  • Do not tag or push without explicit user confirmation.
  • Do not discard unrelated worktree changes.
  • Prefer docs/releases/v<version>-release-notes.md as the blog/release-note source of truth after generation.
  • If git status --porcelain is not clean and the task is a real publish, call that out before invoking publish.sh.

References

  • Read references/release-workflow.md for the step-by-step release decision tree.
  • Read docs/release-guide.md when the task needs the full publish or verification checklist.
Files

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.

Changes

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.

  1. 4d ago First seen · 56 lines · 38 tokens per session scan A 0e5545c82250

Subscribe to this mod's changes

release is a skill published in the GitHub repository phodal/routa (1,808 stars, last pushed 21d ago), licensed MIT. It adds 38 tokens to every session and 511 once invoked, about $0.0002 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-08-30.

Related

Other skills, from other repositories

release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

openai/symphony · 42 tokens

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.

phuryn/pm-skills · 57 tokens

snapshot-release

Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …

daangn/seed-design · 142 tokens

release-notes

Generate GitHub release notes for the Membrane api-gateway repo by collecting the commits between the last release and master, grouping them into Features / Improvements / Fixes / Security / Dependencies, and linking each to its PR. Use whenever the user wants to draft, extract, or write release notes / a changelog /…

membrane/api-gateway · 124 tokens

deploy

Trigger the claude-desktop-extra Build & Release GitHub Actions pipeline (build-and-release.yml). With no argument the skill inspects the changes since the last release and decides forcerebuild itself; "/deploy force" / "/deploy no-force" override.

patrickjaja/claude-desktop-extra · 54 tokens

multi-repo-release

Prepares and validates GPT-RAG umbrella releases across component repositories and the AI Landing Zone. Use for manifest pins, changelog entries, release branches, tags, and GitHub Release notes.

Azure/GPT-RAG · 43 tokens