mcp-server-langgraph: Command for Claude Code

.claude/commands/release-prep.md

release-prep is a command for Claude Code from vishnu2kmohan/mcp-server-langgraph. It costs 5 tokens per session (1,668 once invoked), scanned A, original, MIT.

A release checklist command that checks whether a software version is ready to publish.

In plain words
What is it for?
Checking a version number, running tests, linting, security and type checks, verifying changelog and breaking-change entries, and validating deployment settings.
Why use it?
It gathers tests, code checks, documentation checks, and deployment validation in one repeatable pre-release process.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

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

Reuse

Borrowing it

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

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-prep

README.md
[![agentmods](https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/release-prep/github.svg)](https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/release-prep)
Your own site
<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/release-prep"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/release-prep/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-prep

Your own site · 80×15
<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/release-prep"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/release-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5 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,668 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.00005 $0.01668
Opus 5.5 $0.00002 $0.00667
Sonnet 5.5 $0.00001 $0.00334
Haiku 4.5 $0.00001 $0.00167

Measured 1mo ago against content hash e41b92e83b67, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-prep 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 1mo 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-prep.md · 304 lines

How it starts

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

Release Preparation Checklist

Usage: /release-prep <version>

Example: /release-prep 2.8.0

Purpose: Automated release readiness validation


🚀 Release Preparation Workflow

Step 1: Validate Version Number

Parse and validate version from $ARGUMENTS:

VERSION=$ARGUMENTS

# Validate semantic versioning format
if [[ ! $VERSION =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
    echo "❌ Invalid version format. Use X.Y.Z (e.g., 2.8.0)"
    exit 1
fi

echo "✅ Preparing release v$VERSION"

Step 2: Pre-Release Checklist

Run comprehensive validation:

Code Quality:

# 1. All tests passing
make test-unit
make test-integration
make test-all-quality

# 2. Linting clean
make lint-check

# 3. Security scan
make security-check

# 4. Type checking
mypy src/ --strict

Status: Pass/Fail for each

Documentation:

# 1. CHANGELOG.md updated
grep -q "## \[$VERSION\]" CHANGELOG.md

# 2. Version in pyproject.toml
grep -q "version = \"$VERSION\"" pyproject.toml

# 3. Breaking changes documented
[ -f BREAKING_CHANGES.md ] && grep -q "## $VERSION" BREAKING_CHANGES.md

Deployment Configs:

# 1. Validate all deployment configs
make validate-all

# 2. Check Docker image builds
docker build -t test:$VERSION .

# 3. Verify Helm chart version
grep -q "version: $VERSION" deployments/helm/langgraph-agent/Chart.yaml

Step 3: Generate Release Notes

Create release notes from CHANGELOG.md and git commits:

# Extract changelog section for this version
sed -n "/## \[$VERSION\]/,/## \[/p" CHANGELOG.md > /tmp/release_notes.md

# Add git commit summary since last tag
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~10")
git log $LAST_TAG..HEAD --oneline --no-merges >> /tmp/release_notes_commits.txt

Format:

# Release v$VERSION

**Release Date**: YYYY-MM-DD
**Type**: Major | Minor | Patch

## 🎯 Highlights

- [Key feature 1]
- [Key feature 2]
- [Key improvement]

## ✨ New Features

- [List from CHANGELOG]

## 🐛 Bug Fixes

- [List from CHANGELOG]

## 📚 Documentation

- [Updates]

## ⚠️ Breaking Changes

- [If any]

## 📦 Deployment Notes

- [Any special deployment steps]

## 🔗 Links

- Full Changelog: [link]
- Documentation: [link]

Read the full file on GitHub · 304 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. 1mo ago First seen · 304 lines · 5 tokens per session scan A e41b92e83b67

Subscribe to this mod's changes

release-prep is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 2d ago), licensed MIT. It adds 5 tokens to every session and 1,668 once invoked, about $0.0000 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-31.