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/analyze-code.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/analyze-code)<a href="https://agentmods.dev/commands/mizchi/lsmcp/analyze-code"><img src="https://agentmods.dev/badge/commands/mizchi/lsmcp/analyze-code/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/analyze-code"><img src="https://agentmods.dev/badge/commands/mizchi/lsmcp/analyze-code.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.01682 |
| Opus 5.5 | $0.00000 | $0.00673 |
| Sonnet 5.5 | $0.00000 | $0.00336 |
| Haiku 4.5 | $0.00000 | $0.00168 |
Grade A, and why
analyze-code 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Analysis with LSMCP MCP
This command uses the LSMCP (Language Server MCP) tools to perform rapid semantic code analysis, leveraging language server capabilities for more accurate results than traditional grep/search approaches.
Overview
LSMCP provides semantic code analysis through language server protocol, enabling:
- Type-aware error detection
- Symbol reference tracking
- Cross-file dependency analysis
- Real-time diagnostics
Command Template
# Rapid Code Analysis Task
Project Root: <PROJECT_PATH>
Target Language: <LANGUAGE>
Analysis Goal: <SPECIFIC_GOAL>
Execute the following analysis phases:
## Phase 1: Capability Check (5 seconds)
Verify available LSP features:
mcp__lsmcp-__check_capabilities
## Phase 2: Project-wide Diagnostics (10 seconds)
Collect all errors and warnings:
mcp__lsmcp-__get_all_diagnostics
- root: "<PROJECT_PATH>"
- pattern: "**/*.<FILE_EXTENSION>"
- severityFilter: "error" # Start with errors only
- useGitignore: true
If few errors found, repeat with severityFilter: "warning"
## Phase 3: Symbol Analysis (5 seconds per symbol)
For critical functions/classes:
mcp__lsmcp-__find_references
- root: "<PROJECT_PATH>"
- filePath: "<RELATIVE_FILE_PATH>"
- line: <LINE_NUMBER>
- symbolName: "<SYMBOL_NAME>"
## Phase 4: Type Verification (3 seconds per location)
For suspicious code locations:
mcp__lsmcp-__get_hover
- root: "<PROJECT_PATH>"
- filePath: "<RELATIVE_FILE_PATH>"
- line: <LINE_NUMBER>
- target: "<CODE_SNIPPET>"
## Phase 5: Unused Code Detection
Identify symbols with zero references:
mcp__lsmcp-__find_references
- Check exported functions/classes
- Flag items with 0 references
## Report Format
1. Executive Summary
- Total errors/warnings count
- Critical issues requiring immediate attention
2. Detailed Findings
- Group by severity (Error > Warning > Info)
- Include file:line references
- Show affected symbol names
3. Impact Analysis
- Number of files affected
- Cross-module dependencies
4. Recommendations
- Priority fixes
- Refactoring suggestions
- Code quality improvements
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 · 232 lines · 0 tokens per session scan A 3cbf31f4e25a
analyze-code 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 1,682 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.