A release command that prepares a new Uni-CLI version from a clean main branch. A release is a versioned software package prepared for publication, while main is the project's primary Git branch.

Use it to verify the project, update the version and changelog, create the release commit, and add an annotated Git tag for a specified version and codename.

It keeps version changes, changelog updates, generated files, checks, the release commit, and tag consistent. It also prevents local publishing or pushing without explicit confirmation.

release — Command by olo-dot-io

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/olo-dot-io/uni-cli/release

Clone the repo

git clone --depth 1 https://github.com/olo-dot-io/Uni-CLI

Made for: Claude Code.

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

When invoked 468 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.00000	$0.00468
Opus 5	$0.00000	$0.00234
Sonnet 5	$0.00000	$0.00094
Haiku 4.5	$0.00000	$0.00047

Measured yesterday against content hash b16fe2d69f93, 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 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.

.claude/commands/release.md · 55 lines

What it actually says

/release — atomic version bump + publish

Cut a Uni-CLI release from a clean main.

Usage

/release <version> [codename]

Example: /release 0.212.0 "Shatalov"

What it does

Confirms main is clean and up to date with origin.
Runs npm run verify (must pass).
Runs npm run changeset:version to fold pending changesets into CHANGELOG.md and bump package.json.
Updates the six other files that must change atomically (AGENTS.md counts, README badges/footer, docs/ROADMAP.md progress, docs/TASTE.md current-version, codename series). Handled by scripts/release.ts.
Runs npm run verify again (regenerated AGENTS.md must be clean).
Creates a single commit: release: v<version> — <codename>.
Tags v<version> with annotated message.
Shows what will happen on git push origin main --tags:
- Release workflow triggers, publishes to npm with provenance via OIDC (see contributing/release.md).
- GitHub release drafted from changelog.

Safety

NEVER push without explicit user confirmation.
NEVER run npm publish locally from this command — CI owns publish.
NEVER skip verify — a red build becomes a red published package.
NEVER amend or force-push an existing tag.

What you see

Cut release v0.212.0 — Shatalov

  package.json       0.211.2 → 0.212.0
  CHANGELOG.md       +47 lines
  AGENTS.md          195 → <new> sites, 956 → <new> commands
  README.md          badges updated
  docs/ROADMAP.md    phase 8 marked ✓
  docs/TASTE.md      current version line

Verify: 881 tests passed, build green.

Next step: git push origin main --tags
           (type `y` to push now, `n` to stop here)

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 · 55 lines · 0 tokens per session scan A b16fe2d69f93

Subscribe to this mod's changes

release is a command published in the GitHub repository olo-dot-io/Uni-CLI (270 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 468 tokens. 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.

Browser automation Git and workflow Productivity agent-infrastructure ai-agents ai-tools automation browser-automation cdp

release

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/release — atomic version bump + publish

Usage

What it does

Safety

What you see

What this file has done since we first saw it

Other commands, from other repositories

toon

sync-claude

qa

checkpoint

dream

review-session