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.
npx skills add garretpremo/lsp-mcp-server --skill lsp-searchgit clone --depth 1 https://github.com/garretpremo/lsp-mcp-serverWrote 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/garretpremo/lsp-mcp-server/lsp-search)<a href="https://agentmods.dev/skills/garretpremo/lsp-mcp-server/lsp-search"><img src="https://agentmods.dev/badge/skills/garretpremo/lsp-mcp-server/lsp-search/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/garretpremo/lsp-mcp-server/lsp-search"><img src="https://agentmods.dev/badge/skills/garretpremo/lsp-mcp-server/lsp-search.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.00037 | $0.00371 |
| Opus 5 | $0.00018 | $0.00186 |
| Sonnet 5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
lsp-search 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 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.
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.
What it actually says
LSP Code Navigation & File Search
This skill provides type-aware code navigation and fast file search via language server integration.
When to Use
- find_file — When you need to locate a file by name but don't know the exact path. Faster than globbing. Use before
go_to_definitionwhen you don't have an absolute file path. - go_to_definition — When you need to jump to where a symbol (class, function, variable) is defined. More accurate than grep for finding the actual definition vs. usages.
- find_references — When you need to find everywhere a symbol is used. Essential for understanding impact of changes.
- document_symbols — When you need to understand the structure of a file (classes, methods, fields). Prefer over grep for getting a file overview.
- workspace_symbol — When you need to find a symbol by name across the whole project without knowing which file it's in.
When NOT to Use
- For text/string search — use Grep instead
- For finding files by glob pattern — use Glob instead
- For reading file contents — use Read instead
Tips
- Start with
find_fileif you only have a partial file name - Use enrichment flags (
includeKind,includeContainer) when you need to distinguish between similarly-named symbols workspace_symbolrequires at least one LSP to be running — use any other LSP tool first to start the language server- The
reindextool refreshes the file index if files have been added/removed since the session started
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 · 30 lines · 37 tokens per session scan A 8d7e7a04f77e
lsp-search is a skill published in the GitHub repository garretpremo/lsp-mcp-server (0 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 371 once invoked, about $0.0002 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-31.
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…