ruby_llm-agents: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from adham90/ruby_llm-agents. It costs 0 tokens per session (2,113 once invoked), scanned A, original, MIT.

A release command for publishing a new version of a Ruby package, called a gem, to RubyGems and GitHub.

In plain words
What is it for?
Use it to choose or detect a version change, update release files, create the release, and publish the gem and GitHub release.
Why use it?
It checks the repository and required tools before releasing, reducing mistakes such as publishing from the wrong branch or with uncommitted changes.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

This is adham90/ruby_llm-agents's own configuration. It tells Claude Code how to work on ruby_llm-agents 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 ruby_llm-agents configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/adhameldeeb/dev/ruby_llm-agents.

Reuse

Borrowing it

Nothing to install: this file belongs to adham90/ruby_llm-agents. 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/adham90/ruby_llm-agents/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/adham90/ruby_llm-agents

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/adham90/ruby_llm-agents/release/github.svg)](https://agentmods.dev/commands/adham90/ruby_llm-agents/release)
Your own site
<a href="https://agentmods.dev/commands/adham90/ruby_llm-agents/release"><img src="https://agentmods.dev/badge/commands/adham90/ruby_llm-agents/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/adham90/ruby_llm-agents/release"><img src="https://agentmods.dev/badge/commands/adham90/ruby_llm-agents/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 2,113 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.00000 $0.02113
Opus 5.5 $0.00000 $0.00845
Sonnet 5.5 $0.00000 $0.00423
Haiku 4.5 $0.00000 $0.00211

Measured 2mo ago against content hash 7790b5c72e3f, 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 · 239 lines

How it starts

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

Ruby LLM Agents Release Command

You are automating a gem release for ruby_llm-agents. The user has provided: $ARGUMENTS

Step 1: Prerequisites Check

Verify required tools are available:

which gem && which gh && which bundle

If any are missing, inform the user what needs to be installed and stop.

Step 2: Pre-flight Checks

Run these checks and stop if any fail:

# Check we're on main branch
git branch --show-current

# Check git status is clean
git status --porcelain

# Pull latest changes
git pull --ff-only origin main
  • If not on main branch, warn the user and ask if they want to continue.
  • If there are uncommitted changes, stop and ask the user to commit or stash them.
  • If pull fails, warn and ask if they want to continue.

Step 3: Read Current Version

Read the current version from lib/ruby_llm/agents/core/version.rb. Parse the VERSION = "X.Y.Z" string to extract major, minor, and patch numbers.

Step 4: Determine Version Bump Type

If the user provided an explicit bump type (patch, minor, or major) as $ARGUMENTS, use that.

Otherwise, automatically detect the bump type by analyzing changes since the last git tag:

4a: Gather Change Data

Run these commands to collect change information:

# Get the last tag
git describe --tags --abbrev=0

# Commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline

# Files changed since last tag
git diff --name-only $(git describe --tags --abbrev=0)..HEAD

# Full diff stat
git diff --stat $(git describe --tags --abbrev=0)..HEAD

Also read CHANGELOG.md and look for any unreleased section at the top (a version entry that matches the next version or has no tag yet).

4b: Apply Semver Rules

Analyze ALL of the following signals to determine the bump type:

MAJOR (X+1.0.0) — if ANY of these are true:

  • CHANGELOG has a ### Breaking Changes section in the unreleased entry
  • Commit messages contain BREAKING CHANGE, BREAKING:, or use conventional commit !: suffix (e.g., feat!:, fix!:)
  • Commit messages mention "remove", "drop support", "rename" for public APIs

Read the full file on GitHub · 239 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 · 239 lines · 0 tokens per session scan A 7790b5c72e3f

Subscribe to this mod's changes

release is a command published in the GitHub repository adham90/ruby_llm-agents (138 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,113 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.

Related

release compared with commands from other repositories

release next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
releaseadham90/ruby_llm-agentsCommand13828d agoMITA0Claude Code
release-managerruvnet/RuViewCommand103kyesterdayMITA0Claude Code
release-swarmruvnet/RuViewCommand103kyesterdayMITA0Claude Code
sync-coordinatorruvnet/RuViewCommand103kyesterdayMITA0Claude Code
releasecapazme/mcp-legal-itCommand303d agoApache-2.0A56Claude Code
shipdshakes/compassCommand214d agoMITA14Claude Code
fire-updateThierryN/fire-flowCommand782mo agoMITA10Claude Code