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-inspectgit 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-inspect)<a href="https://agentmods.dev/skills/blackwell-systems/agent-lsp/lsp-inspect"><img src="https://agentmods.dev/badge/skills/blackwell-systems/agent-lsp/lsp-inspect/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/blackwell-systems/agent-lsp/lsp-inspect"><img src="https://agentmods.dev/badge/skills/blackwell-systems/agent-lsp/lsp-inspect.svg" alt="Reviewed on agentmods" width="80" 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.00126 | $0.04142 |
| Opus 5 | $0.00063 | $0.02071 |
| Sonnet 5 | $0.00025 | $0.00828 |
| Haiku 4.5 | $0.00013 | $0.00414 |
Grade A, and why
lsp-inspect 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.
How it starts
The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requires the agent-lsp MCP server.
lsp-inspect
Full code quality audit for a file, package, or directory. Combines LSP batch
analysis (blast_radius) with targeted per-symbol checks and LLM-driven
heuristic analysis. Produces a severity-tiered findings report with confidence
tiers and fix suggestions.
When to Use
- Auditing a package before a release or major refactor
- Finding dead code, untested exports, and error handling gaps in unfamiliar code
- Reviewing code quality of an external codebase for contribution opportunities
- Pre-merge quality gate on a set of changed files
- Batch inspection of an entire directory with ranked output
- Comparing branch changes against main to find newly introduced issues
Input
/lsp-inspect <target> [--checks <type1>,<type2>] [--json] [--top N] [--diff]
Target can be:
- A file path:
/lsp-inspect src/handlers/auth.go - A directory/package:
/lsp-inspect internal/runnables/ - Multiple targets:
/lsp-inspect pkg/a.go pkg/b.go
Directory detection: When target is a directory, walk all .go, .ts, .py
files in it recursively. Produce a ranked report: "Top N findings sorted by
severity then blast radius."
Flags:
--checks <type1>,<type2>: only run listed check types (default: all applicable)--json: emit structured JSON instead of markdown--top N: Maximum findings to report (default 20). Only applies to directory/batch mode.--diff: Only inspect files changed vs main branch. Filter findings to lines within the diff ranges. Output header: "New issues introduced by this branch."
Check Taxonomy
| Check | What it finds | LSP strategy |
|---|---|---|
dead_symbol |
Exported symbol with zero references | Tier 1A: blast_radius batch; Tier 1B: find_references per-symbol |
test_coverage |
Exported symbol with no test callers | Tier 1A: blast_radius test_callers field |
silent_failure |
Error/exception suppressed without re-raise or logging | Read code, identify bare except:, empty if err != nil {}, swallowed returns |
error_wrapping |
Error returned/raised without context | Read code, identify return err without fmt.Errorf wrapping or raise without from |
coverage_gap |
Unhandled input, error path, or code branch | Read code, identify switch/match without default, unchecked type assertions |
doc_drift |
Docstring/comment that doesn't match the actual signature | Compare inspect_symbol hover text against source |
panic_not_recovered |
Unhandled crash in a goroutine or async context | Read code, identify go func() without recover, unguarded .unwrap() |
context_propagation |
Function receives context but creates a fresh root for callees | Read code, identify context.Background() in functions with ctx parameter |
unrecovered_concurrent_entry |
Concurrent entry point without recovery | Read code, identify goroutines/threads/tasks without try-catch or recover |
unchecked_shared_state |
Type assertion or cast on concurrent data structure without safety check | Read code, identify bare .(*Type) on sync.Map, unchecked casts on ConcurrentHashMap |
channel_never_closed |
Channel or queue created but never closed in the same package | Read code + grep, find creation sites without matching close/shutdown |
shared_field_without_sync |
Field accessed from concurrent contexts without synchronization | blast_radius (sync_guarded) + find_callers (cross_concurrent) |
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 · 322 lines · 126 tokens per session scan A 76aecfabaa1f
lsp-inspect is a skill published in the GitHub repository blackwell-systems/agent-lsp (124 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 4,142 once invoked, about $0.0006 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-30.
Other skills, from other repositories
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…
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…
Sverklo Code Intelligence
Gives you deep codebase understanding — semantic search, blast-radius analysis, PR review, and health audits.
cartograph
Explore a codebase through Cartograph v2's PostgreSQL code graph: intent-aware context, exact/BM25/hybrid search, callers/callees/impact, affected tests, live source, review, freshness, and bounded index administration.
qartez
Semantic code intelligence skill for qartez MCP. Use qartez tools for code exploration, impact analysis, and guarded refactors; treat built-in code-tool denials as routing signals and recover via qartez replacements.
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…