Borrowing it
Nothing to install: this file belongs to mizchi/lsmcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mizchi/lsmcp/main/.claude/commands/prerelease-check.mdgit clone --depth 1 https://github.com/mizchi/lsmcpWrote 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/mizchi/lsmcp/prerelease-check)<a href="https://agentmods.dev/commands/mizchi/lsmcp/prerelease-check"><img src="https://agentmods.dev/badge/commands/mizchi/lsmcp/prerelease-check/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.
<a href="https://agentmods.dev/commands/mizchi/lsmcp/prerelease-check"><img src="https://agentmods.dev/badge/commands/mizchi/lsmcp/prerelease-check.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.02226 |
| Opus 5.5 | $0.00000 | $0.00890 |
| Sonnet 5.5 | $0.00000 | $0.00445 |
| Haiku 4.5 | $0.00000 | $0.00223 |
Grade A, and why
prerelease-check 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.
How it starts
The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-release Checklist
This document outlines the verification steps to be performed before releasing lsmcp. The primary focus is to ensure that lsmcp-dev MCP functionality works correctly.
Prerequisites
- Node.js is installed
- Project dependencies are installed (
pnpm install) - Build is completed (
pnpm build) .mcp.jsonhas lsmcp-dev configured
1. Basic Functionality Verification
1.1 MCP Server Startup
# Verify that the MCP server starts correctly in Claude Code
# Uses the lsmcp-dev configuration from .mcp.json
1.2 Tool List Retrieval
# List all available MCP tools from lsmcp-dev server
# Verify that 13 LSP tools are available
Expected: 13 LSP tools should be listed
2. LSP Core Features
2.1 Hover Information
# Use mcp__lsmcp-dev__get_hover
# Example: Get hover info for an import statement in src/mcp/lsmcp.ts
root: /home/mizchi/mizchi/lsmcp
filePath: src/mcp/lsmcp.ts
line: 14
target: debug
Expected: Type information and documentation for the imported function
2.2 Go to Definition
# Use mcp__lsmcp-dev__get_definitions
# Example: Find definition location for functions or classes
root: /home/mizchi/mizchi/lsmcp
filePath: src/mcp/lsmcp.ts
line: <line number>
symbolName: <symbol name>
Expected: File path and line number of the definition
2.3 Find References
# Use mcp__lsmcp-dev__find_references
# Example: Search where a specific function is used
root: /home/mizchi/mizchi/lsmcp
filePath: src/mcp/_mcplib.ts
line: <line number>
symbolName: debug
Expected: List of all locations where the symbol is used
2.4 Get Diagnostics
# Use mcp__lsmcp-dev__get_diagnostics
# Get TypeScript errors and warnings
root: /home/mizchi/mizchi/lsmcp
filePath: <target file>
Expected: Detailed error and warning information if any exist
2.5 Get All Diagnostics
# Use mcp__lsmcp-dev__get_all_diagnostics
# Get errors and warnings for all files in the project
root: /home/mizchi/mizchi/lsmcp
include: **/*.ts
severityFilter: all
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.
- 1mo ago First seen · 337 lines · 0 tokens per session scan A 37e9c31d5f34
prerelease-check is a command published in the GitHub repository mizchi/lsmcp (454 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,226 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.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.