dbatools is a PowerShell toolkit for automating SQL Server administration and moving SQL Server instances between environments. It is for database administrators who manage SQL Server systems and migrations.
Borrowing it
Nothing to install: this file belongs to dataplat/dbatools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dataplat/dbatools/development/.claude/skills/issue/SKILL.mdgit clone --depth 1 https://github.com/dataplat/dbatoolsWrote 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/dataplat/dbatools/issue)<a href="https://agentmods.dev/skills/dataplat/dbatools/issue"><img src="https://agentmods.dev/badge/skills/dataplat/dbatools/issue.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.00049 | $0.02415 |
| Opus 5 | $0.00024 | $0.01208 |
| Sonnet 5 | $0.00010 | $0.00483 |
| Haiku 4.5 | $0.00005 | $0.00242 |
Grade A, and why
issue 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work a dbatools Issue
Take a GitHub issue from "please have a look" to either a pull request or an informed comment.
The two failure modes this skill exists to prevent: fixing something that development already fixed, and fixing one command when the same defect sits in three. Steps 2 and 4 are the ones that earn their keep — do not skip them because the fix looks obvious.
1. Read the whole issue
gh issue view <number> --json number,title,state,author,body,labels,createdAt,comments
Use the --json form, not gh issue view <number> --comments. Those two views are disjoint: the plain view prints the body and no comments, --comments prints the comments and no body. On an issue with no comments yet — which is most new reports — --comments prints nothing at all and looks like a broken gh. The --json form always returns both in one call.
Also check whether someone is already on it:
gh pr list --state open --search "<number>"
git branch -a --list "*<keyword>*"
If a PR already references the issue, stop and report that instead of duplicating the work.
Note what the reporter offered. dbatools reporters frequently say "I can submit a pull request" — that changes the recommendation at the end, it does not stop you from investigating.
2. Verify the report against development
Reporters cite the version they run, which is usually behind. Before diagnosing anything, confirm the defect still exists in the current code:
- Read the actual lines in
public/orprivate/, not the version in the issue text git log -S"<the suspect code>" --oneline -5 -- <file>shows whether it was already touched- If it is already fixed, say so with the commit and the version it shipped in, and propose closing the issue
Take the reporter's analysis seriously — it is often correct and specific — but confirm it in the code yourself before acting on it.
Check the dependency versions too, not just the dbatools version
For anything touching connections, SMO, authentication, encryption or bulk copy, the module version is the less interesting number. The behaviour usually comes from dbatools.library and the Microsoft.Data.SqlClient it ships, and a report is frequently against a library that is months old.
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 · 168 lines · 49 tokens per session scan A 2bbf78edf3ed
issue is a skill published in the GitHub repository dataplat/dbatools (2,829 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 2,415 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
oh-my-posh
Install, configure, or troubleshoot Oh My Posh/ohmyposh: shell init, themes, segments, Nerd Font icons, and prompt setup on PowerShell, zsh, bash, or fish.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
dev-fix
Unified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.
sdlc
Route a task to the next synced SDLC workflow based on current artifacts and repo state.