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 agentmods add skills/perilevy/lsp-intelligence/verifynpx skills add perilevy/lsp-intelligence --skill verifygit clone --depth 1 https://github.com/perilevy/lsp-intelligenceWrote 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/perilevy/lsp-intelligence/verify)<a href="https://agentmods.dev/skills/perilevy/lsp-intelligence/verify"><img src="https://agentmods.dev/badge/skills/perilevy/lsp-intelligence/verify.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00503 |
| Opus 5 | $0.00009 | $0.00251 |
| Sonnet 5 | $0.00003 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
verify 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 3d 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
Verify Changes
Full pre-commit/pre-PR verification in one command. Orchestrates diagnostics, API contract analysis, and test coverage into a single structured verdict.
Steps
-
Call
verify_changeswith the user's base branch (if specified):- If
--base <branch>provided, pass it - Otherwise, let the tool auto-detect the merge base
- If
-
Present the result in this order:
Changed files — list what was modified
Type errors — if
totalErrors > 0:- Show each file with its error count
- Show the first 3 errors per file with line and message
- Offer to run
/whyon the first error for root cause
API changes — if
apiis not null:- Show semver verdict: MAJOR / MINOR / PATCH
- If breaking > 0: list breaking changes with details
- If risky > 0: list risky changes
- Offer to run
/api-checkfor full details
Test gaps — if any
testGapshavehasTests: false:- List untested high-risk symbols with reference counts
- Offer to run
/impact <symbol>for blast radius
Verdict — show the final verdict prominently:
- "safe to merge" — all clear
- "needs attention" — breaking API changes or untested high-risk symbols
- "has errors" — type errors must be fixed first
-
If there are warnings, show them at the bottom.
-
Offer follow-up actions based on verdict:
- has errors: "Want me to fix the errors?" or
/why <file:line> - needs attention: "Want me to check the breaking changes?" or
/api-check - safe to merge: "Ready to commit?" or
/diffto review
- has errors: "Want me to fix the errors?" or
Examples
| Command | What happens |
|---|---|
/verify |
Auto-detect base, check all changed files |
/verify --base main |
Compare against main branch |
/verify --base develop |
Compare against develop branch |
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.
- 3d ago First seen · 55 lines · 17 tokens per session scan A ae274ebfe8a2
verify is a skill published in the GitHub repository perilevy/lsp-intelligence (1 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 503 once invoked, about $0.0001 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…