warren: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from jayminwest/warren. It costs 39 tokens per session (1,293 once invoked), scanned A, original, MIT.

A release command for the Warren project that prepares a version, pushes it, and checks that the automated release process publishes the results.

In plain words
What is it for?
Use it to audit release work, update the version and changelog, create the release commit, push it, and watch the build, container deployment, package publication, and announcement steps.
Why use it?
It removes the need to perform release checks, version updates, changelog editing, and pipeline monitoring by hand. It also verifies that a release reaches its final published state.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; mentions subagents; mentions AGENTS.md.

This is jayminwest/warren's own configuration. It tells Claude Code how to work on warren itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything warren configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jayminwest/warren. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jayminwest/warren/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/jayminwest/warren

Made for: Claude Code.

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/commands/jayminwest/warren/release/github.svg)](https://agentmods.dev/commands/jayminwest/warren/release)
Your own site
<a href="https://agentmods.dev/commands/jayminwest/warren/release"><img src="https://agentmods.dev/badge/commands/jayminwest/warren/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/commands/jayminwest/warren/release"><img src="https://agentmods.dev/badge/commands/jayminwest/warren/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,293 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00039 $0.01293
Opus 5.5 $0.00016 $0.00517
Sonnet 5.5 $0.00008 $0.00259
Haiku 4.5 $0.00004 $0.00129

Measured 2mo ago against content hash ed35ca3425a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.claude/commands/release.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release

Prepare a new warren release, push it, and verify the pipeline shipped it. The release does not exist when the commit lands — it exists when the Release workflow's five-job chain finishes: gates → tag → draft release → ghcr image + GKE deploy → npm publish → promote draft to final → Discord announce. This command runs everything up to the push, then watches that chain to the end.

1. Pre-flight

  • Working tree is clean, on main, up to date with origin (git status, git pull).
  • No open PRs about to auto-merge into the release commit: gh pr list --state open. If one is close to merging, either wait for it or release without it deliberately — never race it.
  • Find the last release tag: git describe --tags --abbrev=0.

2. Tracker audits (two parallel subagents)

Spawn both subagents in a single message so they run concurrently. Neither pushes — all commits ride out with the single push in step 9.

  • Seeds audit — a subagent that invokes the seeds-issue-audit skill and follows it exactly: auto-close only HIGH-confidence issues with citable evidence, run sd sync after closing, report borderline cases, never push. Have it return its two tables (auto-closed / borderline).
  • GitHub issue sweep — a subagent that lists open GitHub issues (gh issue list --state open) and verifies each against HEAD. Same discipline as the seeds audit: close an issue only when the fix is verifiably on main (name the commit or merged PR in the closing comment, gh issue close <n> --comment "..."); anything uncertain goes in a borderline table, untouched. Staleness alone never closes anything.

Hold both reports — the borderline tables go in the final summary (step 10), and confirmed-done plans feed the ROADMAP update (step 6).

3. Review changes since the last tag

  • git log <tag>..HEAD --oneline and git diff <tag>..HEAD --stat.
  • Determine the version bump level. Always use patch unless the user explicitly requests minor or major.

Read the full file on GitHub · 120 lines

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. 2mo ago First seen · 120 lines · 39 tokens per session scan A ed35ca3425a4

Subscribe to this mod's changes

release is a command published in the GitHub repository jayminwest/warren (513 stars, last pushed 7d ago), licensed MIT. It adds 39 tokens to every session and 1,293 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-08-30.

Related

release compared with commands from other repositories

release next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
releasejayminwest/warrenCommand5137d agoMITA39Claude Code
factory-shipwatt-mind/factoryCommand181mo agoApache-2.0A18Claude Code
factory-mergewatt-mind/factoryCommand181mo agoApache-2.0A14Claude Code
factory-workwatt-mind/factoryCommand181mo agoApache-2.0A16Claude Code
sync-coordinatorruvnet/rufloCommand81kyesterdayMITA0Claude Code
github-modesruvnet/rufloCommand81kyesterdayMITA0Claude Code
releasedork-labs/dorkosCommand11yesterdayMITA0Claude Code