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.
npx agentmods add commands/vishnu2kmohan/mcp-server-langgraph/release-prepgit clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraphWrote 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.
[](https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/release-prep)<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="Measured on agentmods" height="20"></a>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.00005 | $0.01668 |
| Opus 5 | $0.00003 | $0.00834 |
| Sonnet 5 | $0.00001 | $0.00334 |
| Haiku 4.5 | $0.00001 | $0.00167 |
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 3d 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.
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]
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.
- 3d ago First seen · 304 lines · 5 tokens per session scan A e41b92e83b67
release-prep is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 10d ago), licensed MIT. It adds 5 tokens to every session and 1,668 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-31.
Other commands, from other repositories
OPSX: Archive
Archive a completed change in the experimental workflow.
hal-voice-toggle
Toggle HAL 9000 voice clips on or off.
pre-release
Run the pre-release checklist for this project. Work through all three phases in order, pausing for explicit confirmation at each decision point before proceeding. Never create a branch, commit, tag, or push without approval.
release-notes
Curate a CHANGELOG.md entry from commits since the last release; with a bump arg, also version, commit, and push the tag — then hand the npm publish to the user (they publish manually). nightly instead cuts a pre-release from the nightly branch. Also flags when the separately-published provider SDK needs a republish.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.
release-plan
Command "release-plan" from alisunstar/OpenSunstar, covering /rd:release-plan — 发布计划, 先读, 执行, 产物 and 人工确认.