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 vanterx/mssql-performance-skills --skill sqldeadlock-reviewgit clone --depth 1 https://github.com/vanterx/mssql-performance-skillsWrote 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/vanterx/mssql-performance-skills/sqldeadlock-review)<a href="https://agentmods.dev/skills/vanterx/mssql-performance-skills/sqldeadlock-review"><img src="https://agentmods.dev/badge/skills/vanterx/mssql-performance-skills/sqldeadlock-review/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/vanterx/mssql-performance-skills/sqldeadlock-review"><img src="https://agentmods.dev/badge/skills/vanterx/mssql-performance-skills/sqldeadlock-review.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00075 | $0.05270 |
| Opus 5 | $0.00037 | $0.02635 |
| Sonnet 5 | $0.00015 | $0.01054 |
| Haiku 4.5 | $0.00007 | $0.00527 |
Grade A, and why
sqldeadlock-review 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 11d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Server Deadlock Analysis Skill
Purpose
Parse a SQL Server deadlock XML graph, identify the victim and winner processes, extract the queries and lock acquisition patterns involved, match against 17 known deadlock patterns (P1–P17), and produce a prioritized remediation plan.
Input
Accept any of:
- Raw
<deadlock>XML (from system_health XE session or SSMS deadlock graph Save As XML) - A file path to a
.xdlor.xmldeadlock graph file - A description of the deadlock if XML is not available
How to Run
- Parse the XML structure
- Extract process list (victim, winner, their queries, lock waits)
- Extract resource list (what locks are held and requested)
- Match against pattern library
- Generate remediation recommendations
XML Structure Reference
<deadlock>
<victim-list>
<victimProcess id="process1a2b" />
</victim-list>
<process-list>
<process id="process1a2b" taskpriority="0" logused="0"
waitresource="KEY: 5:72057594038910976 (abc123)"
waittime="4023" ownerId="123456"
transactionname="user_transaction"
currentdb="5" spid="52" kpid="1234"
status="suspended" isolationlevel="read committed">
<executionStack>
<frame procname="adhoc" line="3" stmtstart="100" stmtend="200"
sqlhandle="0x...">
UPDATE Orders SET Status = 1 WHERE Id = @id
</frame>
</executionStack>
<inputbuf>UPDATE Orders SET Status = 1 WHERE Id = @id</inputbuf>
</process>
...
</process-list>
<resource-list>
<keylock hobtid="72057594038910976" dbid="5" objectname="dbo.Orders"
indexname="PK_Orders" id="lock1" mode="X" associatedObjectId="...">
<owner-list>
<owner id="process2c3d" mode="X" />
</owner-list>
<waiter-list>
<waiter id="process1a2b" mode="U" requestType="wait" />
</waiter-list>
</keylock>
...
</resource-list>
</deadlock>
Extraction Checklist
What ships with it
9 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.
- assets/.gitkeep 0 B
- evals/evals.json 874 B
- examples/deadlock-analysis.md 4.7 KB
- examples/deadlock.xml 3.1 KB
- references/check-explanations.md 26 KB
- references/README.md 1.1 KB
- scripts/01_read_system_health_deadlocks.sql 4.1 KB
- scripts/02_create_dedicated_xe_session.sql 2.8 KB
- scripts/03_read_dedicated_session.sql 2.7 KB
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.
- 11d ago First seen · 345 lines · 75 tokens per session scan A b516ac0e591a
sqldeadlock-review is a skill published in the GitHub repository vanterx/mssql-performance-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 75 tokens to every session and 5,270 once invoked, about $0.0004 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
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
axiom-audit-grdb-performance
Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.
django-perf-review
Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.