vector_mcp: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from sergiobayona/vector_mcp. It costs 0 tokens per session (1,543 once invoked), scanned A, original, MIT.

A step-by-step workflow for releasing a new version of the VectorMCP Ruby gem. A Ruby gem is a packaged Ruby library that can be published for others to install.

In plain words
What is it for?
Use it to prepare a clean main-branch release, compare the local version with RubyGems, and follow the project's release checks.
Why use it?
It checks the branch, local changes, remote updates, and published version before release to reduce avoidable release conflicts.

Command for Claude Code

Written for Claude Code: installed under .claude/.

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

Reuse

Borrowing it

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

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/sergiobayona/vector_mcp/release/github.svg)](https://agentmods.dev/commands/sergiobayona/vector_mcp/release)
Your own site
<a href="https://agentmods.dev/commands/sergiobayona/vector_mcp/release"><img src="https://agentmods.dev/badge/commands/sergiobayona/vector_mcp/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/sergiobayona/vector_mcp/release"><img src="https://agentmods.dev/badge/commands/sergiobayona/vector_mcp/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 1,543 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.01543
Opus 5.5 $0.00000 $0.00617
Sonnet 5.5 $0.00000 $0.00309
Haiku 4.5 $0.00000 $0.00154

Measured 2mo ago against content hash d0bf5a8eb240, 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 · 262 lines

How it starts

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

Release Workflow

Comprehensive workflow for releasing a new version of the VectorMCP Ruby gem following best practices.

Overview

This command guides you through the complete release process for the VectorMCP gem, ensuring all steps are followed correctly and the release is done safely from a clean state.

Steps

1. Pre-release Checks

First, let's verify we're in a clean state and on the main branch:

!git status --porcelain
!git branch --show-current

If there are uncommitted changes, you should commit or stash them first. If you're not on the main branch, switch to it: git checkout main

2. Update from Remote

Ensure we have the latest changes from the remote repository:

!git pull origin main

3. Version Comparison Check

CRITICAL: Compare local version against published gem version to prevent conflicts:

# Check current local version
!grep -n "VERSION" lib/vector_mcp/version.rb

# Check latest published version on RubyGems
!gem list vector_mcp --remote --exact

# Alternative: Check specific version info
!gem query --remote --exact --name vector_mcp

Version Analysis:

  • If local version matches published version → Need to bump version
  • If local version is newer → Ready for release (verify changelog)
  • If local version is older → Update to appropriate new version

4. Documentation Review

CRITICAL: Verify README.md reflects all new features since last release:

# Check commits since last published version tag
!git log --oneline $(git describe --tags --abbrev=0)..HEAD

# Review README.md for feature completeness
!grep -n "## Features\|### Features\|## What's New" README.md

README.md Review Checklist:

  • All new features from commits are documented
  • Installation instructions are current
  • Usage examples reflect new capabilities
  • API documentation matches current version
  • Breaking changes are clearly noted
  • Links and references are working

Common README.md Sections to Update:

  • Features list
  • Installation/Setup instructions
  • Usage examples and code samples
  • API documentation
  • Breaking changes section
  • Known issues or limitations

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

Subscribe to this mod's changes

release is a command published in the GitHub repository sergiobayona/vector_mcp (13 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,543 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
releasesergiobayona/vector_mcpCommand1320d agoMITA0Claude Code
gsd:shipmrboups/xbrainCommand21mo agoMITA18Claude Code
release-managerruvnet/sublinear-time-solverCommand92yesterdayMITA0Claude Code
shipmizukaizen/hive-doctrine-mcpCommand04mo agoMITA0Claude Code
acp.package-publishprmichaelsen/remember-mcpCommand17mo agononeA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code