owners

A utility for querying and changing CODEOWNERS information, service labels, and package ownership in Azure SDK repositories. CODEOWNERS records who is responsible for reviewing particular files or packages.

In plain words
What is it for?
Viewing, adding, or removing code owners, package associations, and service labels, then updating the ownership cache.
Why use it?
It helps check whether packages have the required owners and labels and keeps ownership records current.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/azure/azure-sdk-for-net/owners
Any agent
npx skills add Azure/azure-sdk-for-net --skill owners
Clone the repo
git clone --depth 1 https://github.com/Azure/azure-sdk-for-net

Made for: Claude Code, Codex.

Per session 161 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 665 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00161 $0.00665
Opus 5 $0.00081 $0.00332
Sonnet 5 $0.00032 $0.00133
Haiku 4.5 $0.00016 $0.00067

Measured yesterday against content hash 03a82aa3d407, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

owners 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 yesterday.

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/owners/SKILL.md · 54 lines

What it actually says

Owners

Requires: azure-sdk-mcp server

Tools

Tool Purpose
azsdk_engsys_codeowner_view Query by user, label, package, path
azsdk_engsys_codeowner_add_* Add owners/labels (details)
azsdk_engsys_codeowner_remove_* Remove owners/labels
azsdk_check_service_label Check if service label exists
azsdk_create_service_label Create service label
azsdk_engsys_codeowner_check_package Check if a package has sufficient owners, labels, and service owners
azsdk_engsys_codeowner_update_cache Run the CODEOWNERS cache update pipeline to propagate changes

CLI fallback: azsdk config codeowners CLI when MCP is unavailable.

Repository Resolution

Infer repo from workspace in Azure/azure-sdk-for-* repos. Otherwise, ask.

Workflow

  1. Queryazsdk_engsys_codeowner_view to inspect current state.
  2. Modify — Add/remove owners or labels.
  3. Verify — Re-query to confirm.
  4. Update cache — After all ownership changes are complete, ask the user if they want to run azsdk_engsys_codeowner_update_cache to propagate changes immediately. This is especially important when changes are needed to unblock PRs or releases.

New labels: azsdk_check_service_labelazsdk_create_service_label → PR merged → azsdk_engsys_codeowner_add_package_label. See data model.

Checking Package Readiness

Use azsdk_engsys_codeowner_check_package with a package directoryPath to verify a package has sufficient owners, PR labels, and service owners. This is useful to diagnose why a PR or release is blocked due to missing ownership.

Examples

  • "Add @user to azure-core in azure-sdk-for-python"
  • "Who owns azure-storage-blob?"

Troubleshooting

See troubleshooting for common issues.

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. yesterday First seen · 54 lines · 161 tokens per session scan A 03a82aa3d407

Subscribe to this mod's changes

owners is a skill published in the GitHub repository Azure/azure-sdk-for-net (6,045 stars, last pushed 2d ago), licensed MIT. It adds 161 tokens to every session and 665 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

release-readiness

Assesses ship-readiness for .NET MAUI release branches — Servicing Releases (SR) and Previews — and produces public-safe, copy-ready release handoffs or Loop-page drafts from the resulting evidence. Use for readiness verdicts, release blockers, Preview/SR status, release handoff pages, manual validation instructions…

dotnet/maui · 100 tokens

code-review

Deep code review of PR or materialized candidate-patch changes for correctness, safety, and MAUI conventions. Uses independence-first assessment (code before narrative) and delegates to the maui-expert-reviewer agent for per-dimension sub-agent evaluation. Triggers on: "review code for PR", "code review PR", "review…

dotnet/maui · 110 tokens

dependency-flow

MAUI-specific dependency flow rules, channel conventions, and feed lookup workflows. Use when asked about darc, BAR, Maestro, feeds for .NET MAUI, build promotion, asset lookup, channel mappings, or dependency flow for dotnet/maui. Wraps the maestro-cli skill and maestro MCP tools with MAUI-specific guardrails.

dotnet/maui · 71 tokens

try-fix

Attempts ONE alternative fix for a bug, tests it empirically, and reports results. ALWAYS explores a DIFFERENT approach from existing PR fixes. Use when CI or an agent needs to try independent fix alternatives. Invoke with problem description, test command, target files, and optional hints.

dotnet/maui · 60 tokens

review-test-failures

Classifies PR CI/test failures as likely PR-caused or unrelated, compares against base-branch baseline, and emits an overall merge-readiness verdict. Uses gathered GitHub/AzDO/Helix context and the shared MAUI CI facts.

dotnet/maui · 55 tokens

analyze-sessions

Analyzes your local Copilot CLI sessions for dotnet/maui to drive iterative improvements to the PR-review agent (and other agents, skills, and instruction files). Runs a select → extract → score → judge → cluster → propose → emit-eval loop: a deterministic core ranks your worst / most-expensive sessions, then the…

dotnet/maui · 181 tokens