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 blackwell-systems/agent-lsp --skill lsp-exploregit clone --depth 1 https://github.com/blackwell-systems/agent-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/blackwell-systems/agent-lsp/lsp-explore)<a href="https://agentmods.dev/skills/blackwell-systems/agent-lsp/lsp-explore"><img src="https://agentmods.dev/badge/skills/blackwell-systems/agent-lsp/lsp-explore.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.01683 |
| Opus 5 | $0.00000 | $0.00842 |
| Sonnet 5 | $0.00000 | $0.00337 |
| Haiku 4.5 | $0.00000 | $0.00168 |
Grade A, and why
lsp-explore 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 8d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requires the agent-lsp MCP server.
lsp-explore
"Tell me about this symbol" — hover, implementations, call hierarchy, and references in a single pass. Use when navigating unfamiliar code: you get type info, doc comments, who calls it, what implements it, and every reference site without issuing four separate commands.
Read-only — does not modify any files.
Invocation: User provides a symbol name in dot notation (e.g.
"codec.Encode", "Buffer.Reset"). Optionally provide workspace_root
to scope the search.
Prerequisites
If LSP is not yet initialized, call mcp__lsp__start_lsp with the workspace
root first. Auto-inference applies when file paths are provided.
Phase 1 — Locate the symbol
Call mcp__lsp__go_to_symbol with symbol_path set to the user-provided name:
mcp__lsp__go_to_symbol({
"symbol_path": "Package.SymbolName", // dot notation; e.g. "codec.Encode"
"workspace_root": "<root>" // optional
})
→ returns: file, line, column (1-indexed)
Record the returned file, line, and column. If go_to_symbol returns
nothing, report:
Symbol not found:
<name>Check the dot-notation path (e.g. "Package.Symbol") and ensure the workspace root covers the file.
Stop immediately — do not proceed to Phase 2.
Then open the file so the language server has it in view:
mcp__lsp__open_document({
"file_path": "<file from go_to_symbol>"
})
Phase 2 — Hover (always available)
Call mcp__lsp__inspect_symbol at the definition location:
mcp__lsp__inspect_symbol({
"file_path": "<file from Phase 1>",
"line": <line from Phase 1>,
"column": <column from Phase 1>
})
Store the result as hover_text. If the call fails or returns nothing, set
hover_text to an empty string. Do not stop.
Phase 3 — Implementations (capability-gated)
Call mcp__lsp__get_server_capabilities to see what the server supports:
mcp__lsp__get_server_capabilities()
→ returns: supported_tools list
What ships with it
1 file 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.
- 8d ago First seen · 235 lines · 0 tokens per session scan A 819098639e7e
lsp-explore is a skill published in the GitHub repository blackwell-systems/agent-lsp (122 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,683 tokens. 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 skills, from other repositories
trace-mcp
Use trace-mcp tools for code navigation, impact analysis, and framework-aware queries instead of Read/Grep/Glob/Bash. Activate whenever the agent needs to explore, understand, or modify a codebase that has trace-mcp indexed.
dead-code-cleanup
Use when the user asks about cleanup, removing unused code, refactoring, reducing bundle size, or identifying dead code in a Repowise-indexed codebase (.repowise/ directory exists). Also activates when discussing technical debt, code hygiene, or repository maintenance.
authoring-smell-rules
Add a findsmells rule to mache — a SQL query over the projected code graph that surfaces a code smell (duplication, complexity, dead code, drift). Use when adding or debugging a SmellRule in cmd/smellrules.go or an external $MACHESMELLRULESDIR rule. Covers the SmellRule struct, the standalone-vs-ast table capability…
Sverklo Code Intelligence
Gives you deep codebase understanding — semantic search, blast-radius analysis, PR review, and health audits.
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
analyze-usage
Use when asked to analyze codescout tool usage, check for error patterns, audit tool health, generate a usage report, spot anti-patterns, or clear usage statistics to start fresh.