azure-sdk-for-net: Skill for Claude Code

.github/skills/refresh-arm-sdk-release/SKILL.md

refresh-arm-sdk-release is a skill for Claude Code, Codex from Azure/azure-sdk-for-net. It costs 91 tokens per session (1,368 once invoked), scanned A, original, MIT.

A workflow for preparing a refresh pull request for an Azure Resource Manager SDK package. A refresh updates generated SDK code and related dependency or changelog entries to match a newer API version or generation tag.

In plain words
What is it for?
Use it to create a branch, skip packages that are already released or otherwise ineligible, update the package, refresh its changelog and dependencies, and prepare a pull request.
Why use it?
It provides a defined path for checking whether a package should be refreshed and preparing the repository changes needed for review.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

This is Azure/azure-sdk-for-net's own configuration. It tells Claude Code and Codex how to work on azure-sdk-for-net 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 azure-sdk-for-net configures →

About the project

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.

Azure/azure-sdk-for-net · 6,049 stars · on GitHub

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Azure/azure-sdk-for-net/main/.github/skills/refresh-arm-sdk-release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Azure/azure-sdk-for-net

Made for: Claude Code, Codex.

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 refresh-arm-sdk-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/refresh-arm-sdk-release/github.svg)](https://agentmods.dev/skills/azure/azure-sdk-for-net/refresh-arm-sdk-release)
Your own site
<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/refresh-arm-sdk-release"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/refresh-arm-sdk-release/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 refresh-arm-sdk-release

Your own site · 80×15
<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/refresh-arm-sdk-release"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/refresh-arm-sdk-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,368 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.00091 $0.01368
Opus 5 $0.00046 $0.00684
Sonnet 5 $0.00018 $0.00274
Haiku 4.5 $0.00009 $0.00137

Measured 10d ago against content hash 7250ad7ff316, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

refresh-arm-sdk-release 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 10d 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.

.github/skills/refresh-arm-sdk-release/SKILL.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Refresh ARM SDK Release Skill

When to Use This Skill

Activate only when the user wants an Azure.ResourceManager package refresh PR driven by API-version/tag resolution and dependency/changelog refresh updates.

Scope Boundaries

  • Use this skill only for refresh-style updates (for example regenerated surface alignment, changelog maintenance, dependency version refresh, and refresh PR creation).
  • Do not use this skill for broad or feature-driven package releases, release planning across multiple packages, or non-refresh release orchestration.

Prerequisites

  • Repository: azure-sdk-for-net
  • Target package path is known, for example sdk/dns/Azure.ResourceManager.Dns
  • Access to remote origin and GitHub PR creation
  • Current date available in yyyy-mm-dd format

Workflow

Step 1: Create Branch

  • Fetch latest origin/main.
  • Create a new branch from origin/main.
  • Use a branch name that identifies package and date.

Step 2: Eligibility Check — Skip Conditions

Before doing any further work on a package, check the CHANGELOG.md and skip the package (do not refresh it) if either of the following is true:

  1. Already released: The latest changelog entry does NOT contain (Unreleased) — it already has a release date (e.g., ## 1.2.0 (2026-04-17)). This means a release was already prepared and no new (Unreleased) entry exists to stamp.
  2. Dependencies already up to date: Any changelog entry (across all released versions, not just the latest) already contains upgrade lines for both the current Azure.Core and Azure.ResourceManager versions (resolved from eng/centralpackagemanagement/Directory.Packages.props). If these exact versions were already shipped in any prior release, adding them again provides no value, so skip.

When skipping a package, log it clearly as SKIPPED with the reason, and move on to the next package in the batch.

Step 3: Determine API Version Source in Order

  • Check metadata.json in the package root.
  • If present, use apiVersions value.
  • If metadata.json is missing, check src/autorest.md for an uncommented tag.
  • If tag is missing there, use the require value in src/autorest.md to open the referenced readme.md and read tag under Basic Information.

Read the full file on GitHub · 96 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. 10d ago First seen · 96 lines · 91 tokens per session scan A 7250ad7ff316

Subscribe to this mod's changes

refresh-arm-sdk-release is a skill published in the GitHub repository Azure/azure-sdk-for-net (6,049 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 1,368 once invoked, about $0.0005 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.