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/vanterx/mssql-performance-skills/sqlplan-batchnpx skills add vanterx/mssql-performance-skills --skill sqlplan-batchgit clone --depth 1 https://github.com/vanterx/mssql-performance-skillsWhat 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.00111 | $0.02966 |
| Opus 5 | $0.00056 | $0.01483 |
| Sonnet 5 | $0.00022 | $0.00593 |
| Haiku 4.5 | $0.00011 | $0.00297 |
Grade A, and why
sqlplan-batch 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 2d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Server Execution Plan Batch Analysis Skill
Purpose
Analyze multiple .sqlplan files in bulk — applying the full 108-check ruleset (S1–S36, N1–N72) from sqlplan-review to each plan — and produce a single aggregated dashboard that identifies the most expensive queries, most common violations, and consolidated missing index recommendations.
Input
Accept any of:
- A directory path containing
.sqlplanfiles:/path/to/plans/ - A list of
.sqlplanfile paths - A description of the available plans if files cannot be provided
How to Run
- Enumerate all
.sqlplanfiles in the input - Apply the full check ruleset to each plan (same logic as
sqlplan-review) - Aggregate findings into the summary structures below
- Generate a consolidated missing index script via the same merge rules as
sqlindex-advisor - Write output to
batch-analysis.mdin the same directory
Per-Plan Data to Collect
For each plan, collect:
| Field | Source |
|---|---|
| File name | file system |
| Query text (first 200 chars, for display only; use full StatementText for analysis) | StmtSimple/@StatementText |
| Statement cost | StmtSimple/@StatementSubTreeCost |
| DOP | QueryPlan/@DegreeOfParallelism |
| Memory grant (MB) | MemoryGrantInfo/@GrantedMemory ÷ 1024 |
| Critical issue count | checks fired at Critical severity |
| Warning count | checks fired at Warning severity |
| Spill present | SpillToTempDb/@SpillLevel > 0 |
| Missing index count | <MissingIndexGroup> children count |
| Missing index max impact | max @Impact across all MissingIndexGroups |
| Check IDs fired | list of S/N codes |
Aggregation Structures
1. Top 10 Most Expensive Plans
Rank by StatementSubTreeCost descending. Report:
| Rank | File | Cost | DOP | Memory (MB) | Criticals | Warnings |
|---|
2. Top 10 Plans by Critical Issue Count
Rank by Critical issue count descending, break ties by cost.
What ships with it
8 files 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.
- 2d ago First seen · 297 lines · 111 tokens per session scan A f7f4e0aa7bc6
sqlplan-batch is a skill published in the GitHub repository vanterx/mssql-performance-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 2,966 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-31.
Other skills, from other repositories
PostgreSQL Database Administration
Comprehensive PostgreSQL database administration skill for customer support tech enablement, covering database design, optimization, performance tuning, backup/recovery, and advanced query techniques.
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.