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/csharp-azure-spector-coverage-gaps/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/csharp-azure-spector-coverage-gaps)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/csharp-azure-spector-coverage-gaps"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/csharp-azure-spector-coverage-gaps/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/csharp-azure-spector-coverage-gaps"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/csharp-azure-spector-coverage-gaps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 540 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.00078 | $0.05445 |
| Opus 5 | $0.00039 | $0.02722 |
| Sonnet 5 | $0.00016 | $0.01089 |
| Haiku 4.5 | $0.00008 | $0.00545 |
Grade A, and why
csharp-azure-spector-coverage-gaps 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 12d 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 — 564 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovering and implementing Spector coverage gaps for the Azure C# emitter
Overview
This skill discovers which Spector scenarios the Azure C# emitter (@azure-tools/typespec-csharp) does not yet cover, then implements the missing test(s). Spector scenarios are defined in two packages:
- Standard specs:
@typespec/http-specs— general HTTP client scenarios - Azure specs:
@azure-tools/azure-http-specs— Azure-specific scenarios (core, LRO, paging, resource-manager, etc.)
Two coverage dashboards exist:
| Dashboard | URL | Scope |
|---|---|---|
| Standard | https://typespec.io/can-i-use/http/ | Standard HTTP specs only |
| Azure | https://azure.github.io/typespec-azure/can-i-use/http/ | Standard + Azure specs |
Tip: Comparing the two dashboards reveals Standard scenarios where the Azure emitter lags behind (or ahead of) the core TypeSpec C# emitter in
microsoft/typespec.
Note:
{PKG}refers to<repo-root>/eng/packages/http-client-csharpthroughout this document.
Inputs
You may receive one of:
- "Find coverage gaps" — discover all missing scenarios and present them.
- "Compare Azure vs Standard dashboards" — identify Standard scenarios covered on typespec.io but not on the Azure dashboard (or vice versa).
- Spector spec link — a link to a specific spec under
packages/http-specs/specs/...orpackages/azure-http-specs/specs/.... - Spec name — e.g.,
http/encode/duration,http/azure/core/lro/standard,http/type/union/discriminated.
Output
- A report of coverage gaps (when discovering).
- A comparison table of Standard vs Azure dashboard coverage (when comparing).
- New or updated C# NUnit test file(s) under
{PKG}/generator/TestProjects/Spector.Tests/Http/. - Updated
{PKG}/generator/TestProjects/Spector.Tests/TestProjects.Spector.Tests.csprojif a new project reference is needed. - Regenerated client code (via
Generate.ps1).
Workflow
- Ensure prerequisites are met (npm ci, npm run build)
- Discover coverage gaps or identify the target spec
- Verify the spec is not in the failing specs list
- Generate the C# client for the target spec (unstubbed, or use Test-Spector.ps1)
- Read the generated client to understand the API surface
- Read the TypeSpec scenario file to understand expected behavior
- Find or create the test file
- Implement the test(s) following existing conventions
- Run the tests using
Test-Spector.ps1 -filter "<spec-path>" - Validate all tests pass
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.
- 12d ago First seen · 564 lines · 78 tokens per session scan A 025e71b9f41e
csharp-azure-spector-coverage-gaps is a skill published in the GitHub repository Azure/azure-sdk-for-net (6,049 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 5,445 once invoked, about $0.0004 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
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.
migrate-mstest-v3-to-v4
Use this skill before answering, planning, or editing any MSTest 3.x-to-4.x upgrade or post-upgrade failure. Triggers include "MSTest v4 breaking changes"; CS0507/CS0103/CS1061/CS1615; ExecuteAsync, CallerInfo, DisplayName, or custom TestMethodAttribute; ClassCleanupBehavior; ContainsKey; ThrowsExactly or…
migrate-xunit-to-mstest
Convert .NET tests from xUnit.net v2/v3 to MSTest v4 while preserving VSTest or MTP. Use for replacing xunit packages, Fact/Theory/InlineData/MemberData, assertions, IClassFixture/ICollectionFixture, ITestOutputHelper, TestContext cancellation, traits/Owner, skips, timeouts, and xUnit parallelization. Also use when a…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
archunitnet
Use the open-source free ArchUnitNET library for architecture rules in .NET tests. Use when a repo needs richer architecture assertions than lightweight fluent rule libraries usually provide. USE FOR: the repo uses or wants ArchUnitNET; architecture testing needs richer modeling than simple dependency checks. DO NOT…
csharp-expert
Expert-level C# development with .NET 8+, ASP.NET Core, LINQ, async/await, and enterprise patterns. Use when the user mentions C#, .NET, ASP.NET, enterprise, or Microsoft platforms, or when the task involves Modern C#, Async/Await, LINQ, or ASP.NET Core.