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-fix-allgit 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-fix-all)<a href="https://agentmods.dev/skills/blackwell-systems/agent-lsp/lsp-fix-all"><img src="https://agentmods.dev/badge/skills/blackwell-systems/agent-lsp/lsp-fix-all/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-fix-all"><img src="https://agentmods.dev/badge/skills/blackwell-systems/agent-lsp/lsp-fix-all.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.00048 | $0.01540 |
| Opus 5 | $0.00024 | $0.00770 |
| Sonnet 5 | $0.00010 | $0.00308 |
| Haiku 4.5 | $0.00005 | $0.00154 |
Grade A, and why
lsp-fix-all 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requires the agent-lsp MCP server.
lsp-fix-all
Apply available quick-fix code actions for all current diagnostics in a file, one at a time, re-collecting diagnostics between each fix because line numbers shift after each application.
Important distinction from /lsp-safe-edit: This skill fixes pre-existing
diagnostics in a file — errors and warnings that already exist before any edit
session begins. /lsp-safe-edit has a code-action step (Step 7) for fixing errors
introduced by a specific edit you just made. Use this skill for systematic
bulk-fixing of existing issues, independent of any edit session.
When to use / not use
Use this skill when:
- A file has accumulated errors or warnings you want to resolve automatically
- You want to clean up a file before starting new work
- You want to apply all available language-server quick-fixes in bulk
Do NOT use this skill when:
- You just made an edit and want to fix newly introduced errors — use
/lsp-safe-edit - You want to apply structural refactors — this skill applies quick-fixes only (see filtering below)
- The file has zero diagnostics (the skill will report clean and stop)
Input
- file_path: Absolute path to the file to fix.
Workflow
Step 1 — Open and collect initial diagnostics
Call mcp__lsp__open_document with the target file path to ensure it is loaded
in the language server. Then call mcp__lsp__get_diagnostics to retrieve all
current diagnostics.
If zero diagnostics are returned: report "No diagnostics found — file is clean." and stop. No further steps are needed.
Record the initial count of errors and warnings for the summary output.
Step 2 — Classify and filter code actions
For EACH diagnostic (process one at a time, not in batch):
- Call
mcp__lsp__suggest_fixesat the diagnostic's position/range. - Filter the returned actions to quick-fix kind only.
- Skip any diagnostic for which no applicable quick-fix exists — note it in the summary.
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.
- 10d ago First seen · 179 lines · 48 tokens per session scan A 2775255a6d46
lsp-fix-all is a skill published in the GitHub repository blackwell-systems/agent-lsp (124 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,540 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-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…
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.
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.