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.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/instructions/mizchi/lsmcp/claude-md)<a href="https://agentmods.dev/instructions/mizchi/lsmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/mizchi/lsmcp/claude-md.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.1 | $0.02091 | $0.02091 |
| Opus 5 | $0.01045 | $0.01045 |
| Sonnet 5 | $0.00418 | $0.00418 |
| Haiku 4.5 | $0.00209 | $0.00209 |
Grade A, and why
lsmcp CLAUDE.md 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 6d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL: PRIORITIZE LSMCP TOOLS FOR CODE ANALYSIS
⚠️ PRIMARY REQUIREMENT: You MUST prioritize mcp__lsmcp tools for all code analysis tasks. Standard tools should only be used as a last resort when LSMCP tools cannot accomplish the task.
📋 RECOMMENDED WORKFLOW
1. get_project_overview → Understand the codebase structure
2. search_symbols → Find specific symbols you need
3. get_symbol_details → Get comprehensive information about those symbols
🎯 WHEN TO USE EACH TOOL
For Initial Exploration:
mcp__lsmcp__get_project_overview- First tool to run when exploring a new codebasemcp__lsmcp__list_dir- Browse directory structure when you need to understand file organizationmcp__lsmcp__get_symbols_overview- Get a high-level view of symbols in specific files
For Finding Code:
mcp__lsmcp__search_symbols- Primary search tool for functions, classes, interfaces, etc.mcp__lsmcp__lsp_get_workspace_symbols- Alternative workspace-wide symbol searchmcp__lsmcp__lsp_get_document_symbols- List all symbols in a specific file
For Understanding Code:
mcp__lsmcp__get_symbol_details- Get complete information (type, definition, references) in one callmcp__lsmcp__lsp_get_hover- Quick type information at a specific positionmcp__lsmcp__lsp_get_definitions- Navigate to symbol definition (useincludeBody: truefor full implementation)mcp__lsmcp__lsp_find_references- Find all places where a symbol is used
For Code Quality:
mcp__lsmcp__lsp_get_diagnostics- Check for errors in a specific filemcp__lsmcp__lsp_get_code_actions- Get available fixes and refactorings
For Code Modification:
mcp__lsmcp__lsp_rename_symbol- Safely rename symbols across the codebasemcp__lsmcp__lsp_format_document- Format code according to language conventionsmcp__lsmcp__replace_range- Make precise text replacementsmcp__lsmcp__replace_regex- Pattern-based replacementsmcp__lsmcp__lsp_delete_symbol- Remove symbols and their references
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.
- 6d ago First seen · 198 lines · 2,091 tokens per session scan A bd0a6eb01f56
lsmcp CLAUDE.md is an instructions file published in the GitHub repository mizchi/lsmcp (453 stars, last pushed 10mo ago), licensed MIT. It adds 2,091 tokens to every session, about $0.0105 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.