dbatools: Skill for Claude Code

.claude/skills/issue/SKILL.md

issue is a skill for Claude Code from dataplat/dbatools. It costs 49 tokens per session (2,415 once invoked), scanned A, original, MIT.

A workflow for handling a dbatools issue from investigation through a fix or an informed comment. It checks the issue, existing branches and pull requests, and whether the same defect affects other commands.

In plain words
What is it for?
Use it to investigate GitHub issues, decide whether code changes are needed, test the fix, and prepare a pull request or response.
Why use it?
It reduces duplicated work and helps ensure that a reported problem is fixed consistently across the project.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md; mentions Codex.

This is dataplat/dbatools's own configuration. It tells Claude Code how to work on dbatools itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dbatools configures →

About the project

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.

dataplat/dbatools · 2,858 stars · on GitHub · dbatools.io

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/dataplat/dbatools/development/.claude/skills/issue/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/dataplat/dbatools

Made for: Claude Code.

Wrote 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.

agentmods badge for issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/dataplat/dbatools/issue/github.svg)](https://agentmods.dev/skills/dataplat/dbatools/issue)
Your own site
<a href="https://agentmods.dev/skills/dataplat/dbatools/issue"><img src="https://agentmods.dev/badge/skills/dataplat/dbatools/issue/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.

agentmods 80×15 button for issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/dataplat/dbatools/issue"><img src="https://agentmods.dev/badge/skills/dataplat/dbatools/issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,415 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.02415
Opus 5.5 $0.00020 $0.00966
Sonnet 5.5 $0.00010 $0.00483
Haiku 4.5 $0.00005 $0.00242

Measured 2mo ago against content hash 2bbf78edf3ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/skills/issue/SKILL.md · 168 lines

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/ or private/, 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.

Read the full file on GitHub · 168 lines

Changes

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.

  1. 2mo ago First seen · 168 lines · 49 tokens per session scan A 2bbf78edf3ed

Subscribe to this mod's changes

issue is a skill published in the GitHub repository dataplat/dbatools (2,858 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 2,415 once invoked, about $0.0002 per session on Opus 5.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.

Related

issue compared with skills from other repositories

issue next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
issuedataplat/dbatoolsSkill2.9k4d agoMITA49Claude Code
oh-my-poshJanDeDobbeleer/oh-my-poshSkill24k2d agoMITA47Claude Code, Codex
code-changesJanDeDobbeleer/oh-my-poshSkill24k2d agoMITA48Claude Code, Codex
detecting-fileless-attacks-on-endpointsxalgorix/xalgorixSkill1.3kyesterdayApache-2.0A86Claude Code, Codex
dev-fixHoangNguyen0403/agent-skills-standardSkill583todayMITA43Codex
incident-hotfixHoangNguyen0403/agent-skills-standardSkill583todayMITA27Codex
verify-bugHoangNguyen0403/agent-skills-standardSkill583todayMITA39Codex