A command workflow for preparing a new release of the Roo Code command-line tool, including reviewing changes, updating its version, and writing release notes.

Use it when reviewing changes since the previous release, choosing the version increment, and preparing the changelog.

It provides the required checks and files to update so a CLI release is documented and versioned correctly.

cli-release — Command by RooCodeInc

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 commands/roocodeinc/roo-code/cli-release

Clone the repo

git clone --depth 1 https://github.com/RooCodeInc/Roo-Code

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 635 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.

Model	Per session	Once invoked
Fable 5	$0.00009	$0.00635
Opus 5	$0.00005	$0.00318
Sonnet 5	$0.00002	$0.00127
Haiku 4.5	$0.00001	$0.00064

Measured yesterday against content hash 2539c89c2141, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

cli-release — 100% identical, 0 lines differ
cli-release — 94% identical, 6 lines differ

.roo/commands/cli-release.md · 87 lines

What it actually says

Identify changes since the last CLI release:
- Get the last CLI release tag: gh release list --limit 10 | grep "cli-v"
- View changes since last release: git log cli-v<last-version>..HEAD -- apps/cli --oneline
- Or for uncommitted changes: git diff --stat -- apps/cli
Review and summarize the changes to determine an appropriate changelog entry. Group changes by type:
- Added: New features
- Changed: Changes to existing functionality
- Fixed: Bug fixes
- Removed: Removed features
- Tests: New or updated tests
Bump the version in apps/cli/package.json:
- Increment the patch version (e.g., 0.0.43 → 0.0.44) for bug fixes and minor changes
- Increment the minor version (e.g., 0.0.43 → 0.1.0) for new features
- Increment the major version (e.g., 0.0.43 → 1.0.0) for breaking changes
Update apps/cli/CHANGELOG.md with a new entry:
- Add a new section at the top (below the header) following this format:
```
## [X.Y.Z] - YYYY-MM-DD

### Added

- Description of new features

### Changed

- Description of changes

### Fixed

- Description of bug fixes
```
- Use the current date in YYYY-MM-DD format
- Include links to relevant source files where helpful
- Describe changes from the user's perspective

Create a release branch and commit the changes:

# Ensure you're on main and up to date
git checkout main
git pull origin main

# Create a new branch for the release
git checkout -b cli-release-v<version>

# Commit the version bump and changelog update
git add apps/cli/package.json apps/cli/CHANGELOG.md
git commit -m "chore(cli): prepare release v<version>"

# Push the branch to origin
git push -u origin cli-release-v<version>

Create a pull request for the release:

gh pr create --title "chore(cli): prepare release v<version>" \
    --body "## CLI Release v<version>

This PR prepares the CLI release v<version>.

### Changes
- Version bump in package.json
- Changelog update

### Checklist
- [ ] Version number is correct
- [ ] Changelog entry is complete and accurate
- [ ] All CI checks pass" \
    --base main

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.

yesterday First seen · 87 lines · 9 tokens per session scan A 2539c89c2141

Subscribe to this mod's changes

cli-release is a command published in the GitHub repository RooCodeInc/Roo-Code (24,320 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 635 once invoked, about $0.0000 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.

Git and workflow Productivity Writing and docs

cli-release

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement