Azure SDK for .NET is a repository containing the actively developed C# libraries that applications use to work with Azure services. It is for .NET developers building software that connects to Azure storage, management, and other cloud services.
Borrowing it
Nothing to install: this file belongs to Azure/azure-sdk-for-net. 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/Azure/azure-sdk-for-net/main/.github/skills/pre-commit-checks/SKILL.mdgit clone --depth 1 https://github.com/Azure/azure-sdk-for-netWrote 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/azure/azure-sdk-for-net/pre-commit-checks)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/pre-commit-checks"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/pre-commit-checks/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/azure/azure-sdk-for-net/pre-commit-checks"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/pre-commit-checks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.01603 |
| Opus 5.5 | $0.00019 | $0.00641 |
| Sonnet 5.5 | $0.00010 | $0.00321 |
| Haiku 4.5 | $0.00005 | $0.00160 |
Grade A, and why
pre-commit-checks 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 1mo 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Commit Validation Checks
Run these checks after making changes to SDK packages under sdk/ and before staging, committing, or pushing. These steps may produce additional file changes that must be included in the commit.
General rule: Steps 3–5 are conditional to save time, but if you are unsure whether a step is needed, always run it. It is better to run an unnecessary script than to miss a required regeneration.
1. Determine scope from changed files
- Derive the changed file list from
git status --porcelain(or by combininggit diff --name-only HEADwithgit ls-files -o --exclude-standard) so that untracked (new) files are included. - From the changed file list, extract all unique ServiceDirectories — the first path segment after
sdk/(e.g.,sdk/storage/...→storage,sdk/ai/...→ai). - For each ServiceDirectory, identify all affected packages = distinct
sdk/{ServiceDirectory}/{PackageName}/paths. - For each affected package, identify:
- All csproj files that had changes beneath them (src, tests, samples, perf, stress, or any other project type).
- The src csproj specifically =
sdk/{service}/{package}/src/{Package}.csproj— this is used for GenerateCode.
- The remaining steps must be run for each affected project/ServiceDirectory. If changes span multiple ServiceDirectories or packages, run for each one.
2. Run dotnet format (for every changed csproj)
For every csproj that had files change beneath it — src, tests, samples, perf, stress, or any other project type — run:
dotnet format <path-to-changed.csproj>
Identify affected csproj files by looking at the full changed file list: include any project where either (a) there is a changed .cs file with that .csproj as its nearest parent, or (b) the .csproj itself changed, or files such as .props, .targets, or .md changed under that project. This fixes style/formatting issues and may modify .cs files.
3. Conditionally run dotnet build /t:GenerateCode (per src csproj)
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.
- 1mo ago First seen · 115 lines · 48 tokens per session scan A 9dcc926ed2ef
pre-commit-checks is a skill published in the GitHub repository Azure/azure-sdk-for-net (6,074 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,603 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-08-30.
Other skills, from other repositories
cosmos-pre-commit-validation
Run pre-commit checks for a specific set of crates. Use this when validating changes under sdk/cosmos before committing or during code review.
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
release-notes
Update CHANGELOG.md and README.md for an Azure SDK for Java package based on a GitHub PR. Use when the user wants to write or update release notes, changelogs, or readme docs from a PR reference.
dup-classes
Verify whether generated Java classes duplicate openai-java models by comparing fields/types (names may differ). Use when checking for duplicate model coverage.
codegen
Generate code from TypeSpec via tsp-client (update, sync, generate). Requires a tsp-location.yaml in the current working directory. Supports updating the commit hash before running.
run-tests
Run project tests using Maven (mvn). Use when the user asks to run tests.