Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ashaykubal/essential-agents-skillsnpx agentmods add skills/ashaykubal/essential-agents-skills/setup-lspWrote 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/skills/ashaykubal/essential-agents-skills/setup-lsp)<a href="https://agentmods.dev/skills/ashaykubal/essential-agents-skills/setup-lsp"><img src="https://agentmods.dev/badge/skills/ashaykubal/essential-agents-skills/setup-lsp/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/skills/ashaykubal/essential-agents-skills/setup-lsp"><img src="https://agentmods.dev/badge/skills/ashaykubal/essential-agents-skills/setup-lsp.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.00036 | $0.02932 |
| Opus 5 | $0.00018 | $0.01466 |
| Sonnet 5 | $0.00007 | $0.00586 |
| Haiku 4.5 | $0.00004 | $0.00293 |
Grade B, and why
setup-lsp scanned grade B 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 10d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- [ ] **Stage 4 — Settings**: `ENABLE_LSP_TOOL=1` set in `~/.claude/settings.json` and shell profile This is a copy
95% identical to setup-lsp — 632 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup LSP
Configure Language Server Protocol integration for Claude Code projects. LSP replaces text-based grep/glob searches with semantic code intelligence: go-to-definition, find-references, hover type info, call hierarchy, and real-time error detection.
Mandatory Execution Checklist (BINDING)
Every applicable item below is mandatory. No deviations. No substitutions. No skipping.
This skill uses a 9-stage pipeline. You are the orchestrator. Follow every item in order. Do NOT return to the user until all applicable items are checked.
- Stage 1 — Parse: Arguments read, MODE determined (
full|verify|troubleshoot),--langextracted if present - Stage 2 — Detect:
references/server-registry.mdloaded, manifest files scanned, DETECTED_LANGUAGES presented to user - Stage 3 — Binaries: Binary install command run for each confirmed language
- Stage 4 — Settings:
ENABLE_LSP_TOOL=1set in~/.claude/settings.jsonand shell profile - Stage 5 — Guide Plugin Install: Present user with exact plugin names and instructions to install via
/pluginor CLI - Stage 6 — Checkpoint: Session ID captured via
${CLAUDE_SESSION_ID}, exactclaude --resumecommand presented to user, execution STOPPED - Stage 7 — Verify: (on
--verify) Debug log read,Total LSP servers loaded: Nchecked - Stage 8 — Diagnostics: (if verification failed or
--troubleshoot)references/troubleshooting.mdloaded, issues checked in order - Stage 9 — Report:
templates/diagnostic-output.yamlloaded, diagnostic YAML written tologs/diagnostics/, summary presented to user
Do NOT declare complete until all applicable checkboxes are marked.
When to Use This Skill
| Trigger Pattern | Scenario | Mode |
|---|---|---|
| Starting LSP setup from scratch | Project has no LSP configured | Full setup (no flags) |
| After restarting Claude Code following plugin install | Session resumed, verifying LSP loaded | --verify |
| LSP tools not appearing or servers not responding | Debugging a broken LSP configuration | --troubleshoot |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 313 lines · 36 tokens per session scan B 1520b29f4377
setup-lsp is a skill published in the GitHub repository ashaykubal/essential-agents-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 2,932 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 95% identical to setup-lsp, differing in 632 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…