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/azsdk-common-generate-sdk-locally/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/azsdk-common-generate-sdk-locally)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/azsdk-common-generate-sdk-locally"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/azsdk-common-generate-sdk-locally/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/azsdk-common-generate-sdk-locally"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/azsdk-common-generate-sdk-locally.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 41 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 90 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00202 | $0.01723 |
| Opus 5 | $0.00101 | $0.00861 |
| Sonnet 5 | $0.00040 | $0.00345 |
| Haiku 4.5 | $0.00020 | $0.00172 |
Grade A, and why
azsdk-common-generate-sdk-locally 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 13d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- azsdk-common-generate-sdk-locally — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate SDK Locally
This skill generates, builds, and tests Azure SDKs locally from TypeSpec with automatic customization support, covering the end-to-end workflow for fixing generation issues, applying SDK-specific updates, and refreshing package metadata when needed.
Triggers
USE FOR: generate, build, and test Azure SDKs locally from TypeSpec with automatic customization; update changelog; fix SDK build errors; fix breaking changes; resolve SDK generation errors; customize TypeSpec; rename SDK client or model; hide operation from SDK; fix analyzer errors; resolve customization drift; create subclient; update metadata; update version WHEN: "generate SDK locally", "build SDK", "run SDK tests", "update changelog", "fix SDK build errors", "fix breaking changes", "resolve SDK generation errors", "customize TypeSpec", "rename SDK client", "rename SDK model", "hide operation from SDK", "fix analyzer errors", "resolve customization drift", "create subclient", "update metadata", "update version" DO NOT USE FOR: publishing to package registries, CI pipeline configuration, API design review
Rules
- Requires the
azure-sdk-mcpserver for the MCP workflow; without MCP, usenpm exec --prefix eng/common/tsp-client -- tsp-clientCLI. - Verify the target language repo and the correct TypeSpec configuration file before generation.
- After generation or customization, run the check and test steps before updating metadata or finalizing changes.
MCP Tools
| Tool | Purpose |
|---|---|
azure-sdk-mcp:azsdk_verify_setup |
Verify environment |
azure-sdk-mcp:azsdk_package_generate_code |
Generate SDK |
azure-sdk-mcp:azsdk_package_build_code |
Build package |
azure-sdk-mcp:azsdk_package_run_check |
Validate package |
azure-sdk-mcp:azsdk_package_run_tests |
Run tests |
azure-sdk-mcp:azsdk_customized_code_update |
Apply customizations (includes regeneration and build) |
azure-sdk-mcp:azsdk_package_update_changelog_content |
Update changelog |
azure-sdk-mcp:azsdk_package_update_metadata |
Update metadata including ci.yml |
azure-sdk-mcp:azsdk_package_update_version |
Update version |
What ships with it
5 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.
- 13d ago First seen · 91 lines · 202 tokens per session scan A f96e0260df64
azsdk-common-generate-sdk-locally is a skill published in the GitHub repository Azure/azure-sdk-for-net (6,049 stars, last pushed today), licensed MIT. It adds 202 tokens to every session and 1,723 once invoked, about $0.0010 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-30.
Other skills, from other repositories
cosmos-design-struct
Enforce consistent struct design conventions across sdk/cosmos crates. Validates visibility modifiers, field privacy, #[nonexhaustive] usage, and construction API patterns (Default/new with with setters, or optional separate builders with builder()/build()), and construction correctness on public structs. Can auto-fix…
cosmos-run-integration-tests
Run azure-cosmos integration/customer-workflow tests locally, closely following the CI pipeline (build+install, then failsafe verify with a test profile) using one consistent JDK for both steps. USE WHEN: asked to run cosmos integration tests, customer-workflow tests (fi-customer-workflows / fi-sm-customer-workflows)…
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.
run-tests
Run project tests using Maven (mvn). Use when the user asks to run tests.
test-proxy
Push test-proxy recordings/assets using the test-proxy CLI (e.g., test-proxy push -a assets.json). Use when publishing recordings.
cu-sdk-common-knowledge
Domain knowledge for Azure AI Content Understanding. Use this skill to answer questions about Content Understanding concepts, analyzers, field schemas, API operations, and Java SDK usage. Always consult official documentation before answering.