lsp-intelligence: Instructions file for Claude Code

CLAUDE.md

lsp-intelligence CLAUDE.md is an instructions file for Claude Code from perilevy/lsp-intelligence. It costs 817 tokens per session, scanned A, original, MIT.

Instructions for using local code intelligence in Claude Code when working with TypeScript and JavaScript.

In plain words
What is it for?
Finding code by intent, locating structural patterns and references, tracing root causes, guarding API contracts, and checking changes before merging.
Why use it?
They explain which tools to use for finding code, tracing errors, checking API changes, and verifying edits, while noting when ordinary search is still useful.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is perilevy/lsp-intelligence's own configuration. It tells Claude Code how to work on lsp-intelligence 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 lsp-intelligence configures →

Reuse

Borrowing it

Nothing to install: this file belongs to perilevy/lsp-intelligence. 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/perilevy/lsp-intelligence/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/perilevy/lsp-intelligence

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 lsp-intelligence CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/perilevy/lsp-intelligence/claude-md/github.svg)](https://agentmods.dev/instructions/perilevy/lsp-intelligence/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/perilevy/lsp-intelligence/claude-md"><img src="https://agentmods.dev/badge/instructions/perilevy/lsp-intelligence/claude-md/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 lsp-intelligence CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/perilevy/lsp-intelligence/claude-md"><img src="https://agentmods.dev/badge/instructions/perilevy/lsp-intelligence/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 817 This file is loaded in full into every session.
When invoked 817 The same file — it is already loaded in full.
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.00817 $0.00817
Opus 5.5 $0.00327 $0.00327
Sonnet 5.5 $0.00163 $0.00163
Haiku 4.5 $0.00082 $0.00082

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

Security

Grade A, and why

lsp-intelligence 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 2mo 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.md · 76 lines

How it starts

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

LSP Intelligence — Agent Instructions

Local code intelligence for real engineering workflows. Find code, explain failures, guard API contracts.

Note: The first query in a new session may take a few seconds while the TypeScript engine warms up. The workspace index is persisted and loads instantly on repeat sessions. Subsequent queries are 100-300ms.

Primary tools

Workflow Tool Skill
Find code by intent find_code /find
Find structural patterns find_pattern —
Trace root cause of an error root_cause_trace /why
Check API contract changes api_guard /api-check
Full pre-merge verification verify_changes /verify

When to use LSP tools

You want to... Instead of... Use
Find where an API is used grep "symbolName" find_code or find_references
Find implementations by concept Multiple greps find_code (auto-routes to behavior search)
Find structural patterns Manual code reading find_code or find_pattern
Find config/route/flag definitions Grepping JSON/YAML find_code with config focus
Jump to a definition Reading imports goto_definition
Understand a type signature Reading the source file hover
See what a file contains read on the whole file outline
Know what breaks if you change something Manual tracing impact_trace
Prepare context for a coding task Reading 5-10 files gather_context
Check for type errors after editing Running tsc live_diagnostics
Understand a TypeScript error Reading error + source explain_error / /why
Review what you changed semantically git diff semantic_diff

When to still use grep

  • Searching for string literals in comments or logs
  • Searching non-code files where LSP has no coverage
  • Simple text matching where code-aware ranking isn't needed

Workflow patterns

Read the full file on GitHub · 76 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. 2mo ago First seen · 76 lines · 817 tokens per session scan A 802d908c9c9d

Subscribe to this mod's changes

lsp-intelligence CLAUDE.md is an instructions file published in the GitHub repository perilevy/lsp-intelligence (1 stars, last pushed 7mo ago), licensed MIT. It adds 817 tokens to every session, about $0.0033 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.

Related

lsp-intelligence CLAUDE.md compared with instructions from other repositories

lsp-intelligence CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
lsp-intelligence CLAUDE.mdperilevy/lsp-intelligenceInstructions file17mo agoMITA817Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode