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 sqlbootstraplog-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/sqlbootstraplog-review)<a href="https://agentmods.dev/skills/vanterx/mssql-performance-skills/sqlbootstraplog-review"><img src="https://agentmods.dev/badge/skills/vanterx/mssql-performance-skills/sqlbootstraplog-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.00187 | $0.05823 |
| Opus 5 | $0.00093 | $0.02912 |
| Sonnet 5 | $0.00037 | $0.01165 |
| Haiku 4.5 | $0.00019 | $0.00582 |
Grade A, and why
sqlbootstraplog-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 7d 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 — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SQL Server Setup Bootstrap Log Review Skill
Purpose
Analyze SQL Server Setup Bootstrap log artifacts to find why an installation, upgrade, patch (CU/SP), repair, or cluster node operation failed — and to flag risky setup-time configuration before it becomes production drift. Applies 24 checks (U1–U24) across four categories:
- U1–U6 — Summary and outcome: final result failure, exit-code extraction, failed rules, partial feature failure, patch/upgrade per-instance failures, component update phase failures
- U7–U13 — Rule-failure patterns: pending reboot, disk space, account/permission, prerequisites, cluster rules, policy blockers, Global Rules phase
- U14–U18 — Detail.txt and MSI forensics: end-of-file exceptions, MSI "Return value 3", setup crashes, failure-chain root-cause ordering, Datastore state files
- U19–U24 — ConfigurationFile.ini review: service accounts, instant file initialization, TempDB layout, security surface, feature sprawl, directory placement
Setup runs three phases — (1) Global Rules verification, (2) Component update,
(3) the user-requested action — and writes a dated log folder per run. This skill is the
installation-layer counterpart to sqlerrorlog-review (runtime) and sqldbconfig-review
(post-install drift).
Input
Accept any of:
- Summary.txt or
Summary_<MachineName>_<yyyyMMdd_HHmmss>.txt— overall result, machine properties, discovered features, user input settings, detailed per-feature results, rules with failures or warnings - Detail.txt — time-ordered action execution log; errors and exceptions appear at the end of the file
- MSI / MSP log files (
<Feature>_<Architecture>_<Interaction>.log) — msiexec package logs - ConfigurationFile.ini — the input settings recorded for the run (reusable for unattended installs; passwords and PID are not saved into it)
- SystemConfigurationCheck_Report.htm content (pasted as text) — rule names, short descriptions, and execution status
%temp%\sqlsetup*.log— logs from unattended-mode runs- A natural-language description ("setup failed with 0x851A001A installing the engine")
What ships with it
7 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.
- 7d ago First seen · 428 lines · 187 tokens per session scan A 0447333c5cf2
sqlbootstraplog-review is a skill published in the GitHub repository vanterx/mssql-performance-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 187 tokens to every session and 5,823 once invoked, about $0.0009 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.
byted-bytehouse-slow-query
A ByteHouse tool for finding slow database queries, examining how they run, and suggesting ways to improve them.