install-lsp

install-lsp is a skill for Claude Code from jpoutrin/product-forge. It costs 31 tokens per session (1,576 once invoked), scanned C, original, MIT.

A setup guide for Language Server Protocol integration, which gives code tools semantic knowledge of programming symbols and errors. It can enable actions such as going to a definition, finding references, renaming symbols, and showing diagnostics.

In plain words
What is it for?
Use it to configure language-specific code intelligence for Python, JavaScript or TypeScript, Go, Rust, C or C++, and Java.
Why use it?
It helps an agent navigate and understand code across files more accurately than plain text searches.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the claude-code-dev plugin — 17 skills, 2 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/jpoutrin/product-forge/install-lsp
Any agent
npx skills add jpoutrin/product-forge --skill install-lsp
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

Or install claude-code-dev, the plugin that ships this one along with the rest of its 17 skills, 2 hooks.

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 install-lsp

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/install-lsp.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/install-lsp)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/install-lsp"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/install-lsp.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,576 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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.00031 $0.01576
Opus 5 $0.00015 $0.00788
Sonnet 5 $0.00006 $0.00315
Haiku 4.5 $0.00003 $0.00158

Measured 6d ago against content hash eb3f0abaac36, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade C, and why

install-lsp scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf ~/.claude/plugins/cache
plugins/claude-code-dev/skills/install-lsp/SKILL.md · 198 lines

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.

Install LSP for Claude Code

Enable Language Server Protocol integration to give Claude Code IDE-like code intelligence: go-to-definition, find-references, rename-symbol, and real-time diagnostics.

Why LSP?

LSP provides semantic code understanding instead of text-based grep searches:

  • 50ms to find function call sites with LSP vs 45 seconds with text search
  • Exact symbol locations with line/column numbers
  • Cross-file navigation and refactoring support

Setup Options

Option 1: Native LSP Tool (Recommended)

Claude Code has built-in LSP support that requires activation.

Enable permanently (add to ~/.zshrc or ~/.bashrc):

export ENABLE_LSP_TOOL=1

Install language plugins from the community marketplace:

# Add the LSP plugin marketplace
/plugin marketplace add boostvolt/claude-code-lsps

# Install language-specific plugins
/plugin install pyright@claude-code-lsps        # Python
/plugin install vtsls@claude-code-lsps          # TypeScript/JavaScript
/plugin install gopls@claude-code-lsps          # Go
/plugin install rust-analyzer@claude-code-lsps  # Rust
/plugin install clangd@claude-code-lsps         # C/C++
/plugin install jdtls@claude-code-lsps          # Java
/plugin install omnisharp@claude-code-lsps      # C#
/plugin install intelephense@claude-code-lsps   # PHP
/plugin install kotlin-language-server@claude-code-lsps  # Kotlin
/plugin install solargraph@claude-code-lsps     # Ruby
/plugin install vscode-html-css@claude-code-lsps # HTML/CSS

Option 2: cclsp MCP Server

Community MCP server with interactive setup wizard.

Automated setup:

npx cclsp@latest setup          # Project-level config
npx cclsp@latest setup --user   # User-wide config

The wizard:

  1. Scans project files to detect languages
  2. Pre-selects appropriate LSP servers
  3. Shows installation instructions for each server
  4. Optionally auto-installs LSP binaries
  5. Configures MCP integration

LSP Server Requirements by Language

Read the full file on GitHub · 198 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. 6d ago First seen · 198 lines · 31 tokens per session scan C eb3f0abaac36

Subscribe to this mod's changes

install-lsp is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 1,576 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens