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/sqlprocstats-reviewnpx skills add vanterx/mssql-performance-skills --skill sqlprocstats-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/sqlprocstats-review)<a href="https://agentmods.dev/skills/vanterx/mssql-performance-skills/sqlprocstats-review"><img src="https://agentmods.dev/badge/skills/vanterx/mssql-performance-skills/sqlprocstats-review.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.1 | $0.00080 | $0.07091 |
| Opus 5 | $0.00040 | $0.03546 |
| Sonnet 5 | $0.00016 | $0.01418 |
| Haiku 4.5 | $0.00008 | $0.00709 |
Grade A, and why
sqlprocstats-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 5d 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Server Procedure Stats Review Skill
Purpose
Analyze runtime statistics collected from sys.dm_exec_procedure_stats,
sys.dm_exec_trigger_stats, and sys.dm_exec_function_stats into the collect.proc_stats
table. Applies 25 checks (R1–R25) across five categories:
- R1–R5 — Top resource consumers: identify which procedure, trigger, or function is burning the most CPU, reads, or elapsed time in the collection interval
- R6–R10 — Per-execution efficiency: flag objects that are expensive per call regardless of how often they run — high average CPU, high reads, parameter sniffing signals, spills
- R11–R15 — Pattern detection: N+1 callers, chatty high-frequency procs, plan instability, workload concentration, infrequent-but-heavy outliers
- R16–R20 — Trend analysis: worsening CPU/reads across snapshots, execution spikes, plan changes, new high-cost entries (requires ≥ 3 snapshots from Q5)
- R21–R25 — Advanced runtime patterns: natively compiled proc regression, high CLR ratio, trigger-dominated elapsed time, parallel-to-serial regression, Query Store plan instability
Input
Accept any of:
- Q1 output (Top CPU) — paste the result grid from
04_report_queries.sqlQuery 1 - Q2 output (Top Reads) — paste Query 2 result grid
- Q3 output (Top Callers) — paste Query 3 result grid
- Q4 output (Per-Execution Averages) — paste Query 4 result grid
- Q5 output (Trend / Time Series) — paste Query 5 result grid (requires ≥ 3 snapshots)
- Combined paste — paste two or more query outputs together; apply all applicable checks
- Natural language description — describe the metrics you see ("usp_GetOrders uses 80% of CPU")
- Statement-level stats — paste output from
collect.query_statsusing the report query inscripts/collection/12_report_all_collections.sqlSection 2; all R-checks apply equally to statement-level data — just note the object_name may be NULL for ad-hoc SQL
For trend checks (R16–R20), Q5 output with ≥ 3 rows per object is required. State "Cannot evaluate R16–R20 — trend data not provided" if Q5 is absent.
What ships with it
22 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 937 B
- examples/proc_stats_output-analysis.md 13 KB
- examples/proc_stats_output.txt 2.9 KB
- examples/proc_stats_trend-analysis.md 7.2 KB
- examples/proc_stats_trend.txt 2.5 KB
- references/check-explanations.md 34 KB
- references/README.md 1.1 KB
- scripts/collection/00_bootstrap.sql 3.6 KB
- scripts/collection/01_create_tables.sql 8.1 KB
- scripts/collection/02_usp_collect_procstats.sql 15 KB
- scripts/collection/03_usp_calculate_deltas.sql 9.3 KB
- scripts/collection/04_report_queries.sql 10 KB
- scripts/collection/05_create_agent_job.sql 4.7 KB
- scripts/collection/06_usp_collect_wait_stats.sql 13 KB
- scripts/collection/07_usp_collect_query_stats.sql 18 KB
- scripts/collection/08_usp_collect_file_io.sql 12 KB
- scripts/collection/09_usp_collect_memory.sql 10 KB
- scripts/collection/10_usp_collect_perf_counters.sql 11 KB
- scripts/collection/11_usp_collect_all.sql 2.8 KB
- scripts/collection/12_report_all_collections.sql 6.8 KB
- scripts/collection/Deploy-DmvCollection.ps1 9.2 KB runs code
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.
- 5d ago First seen · 397 lines · 80 tokens per session scan A 9b7c43cd6af3
sqlprocstats-review is a skill published in the GitHub repository vanterx/mssql-performance-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 7,091 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
oracle-expert
Expert in Oracle Database, PL/SQL programming, Oracle RAC, Data Guard, performance tuning, backup/recovery, and enterprise database administration. Use when the user mentions database, enterprise, ERP, PL/SQL, Oracle RAC, or Data Guard, or when the task involves Oracle Architecture, PL/SQL Programming, Performance &…
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.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
debugging
How to debug tursodb using Bytecode comparison, logging, ThreadSanitizer, deterministic simulation, and corruption analysis tools.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…