Azure/AKS-Skills is a collection of agent skills for operating Azure Kubernetes Service clusters after they are provisioned. It helps compatible coding agents investigate incidents, control costs, assess AKS Automatic readiness, run GPU and inference workloads, capture packet-level evidence, and design clusters. The catalogue entries provide the skills, MCP integration, and plugin configuration for these AKS operations.
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.
npx skills add Azure/AKS-Skills --skill aks-known-issuesgit clone --depth 1 https://github.com/Azure/AKS-SkillsWrote 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/aks-skills/aks-known-issues)<a href="https://agentmods.dev/skills/azure/aks-skills/aks-known-issues"><img src="https://agentmods.dev/badge/skills/azure/aks-skills/aks-known-issues/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/aks-skills/aks-known-issues"><img src="https://agentmods.dev/badge/skills/azure/aks-skills/aks-known-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00242 | $0.02666 |
| Opus 5 | $0.00121 | $0.01333 |
| Sonnet 5 | $0.00048 | $0.00533 |
| Haiku 4.5 | $0.00024 | $0.00267 |
Grade A, and why
aks-known-issues 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AKS Known Issues
Turn a specific AKS error code or message into a documented diagnosis: the cause, the Microsoft-documented fix or workaround, and the reference that proves it. This skill is a deterministic string→diagnosis matcher, not an open-ended investigation — it fires when the failure already names itself (an error code, an extension exit code, a rejected value) and you want the known answer fast.
Operating rules
Read-only by default. Do not upgrade, reimage, delete, reconcile, scale, or modify role assignments on the cluster or its Azure resources unless the user explicitly asks. Match the error, explain the cause, cite the documented fix — then apply it only on explicit approval.
Match on the signature, not the vibe. Only claim a known issue when the actual error string matches the entry (code, message, and the operation that produced it). Compare error codes as exact values, not substrings: ZonalAllocationFailed is not the AllocationFailed code. If the symptom is generic and no specific error code is present, this is not the right skill — route to aks-troubleshooting.
Cite the source. Every match names its Microsoft Learn reference so the user (or a support engineer) can verify the fix before acting. If you cannot cite a documented source, say so and hand off — do not invent a "known issue."
How to use
- Capture the exact failure — the error code, the full message, and the operation (
az aks nodepool showon aprovisioningState=Failedpool surfaces the code; VM-extension failures surfacevmssCSEexit codes; ARM/CLI returns the error verbatim). - Match it against the table below (common set) or references/error-code-map.md (full catalog).
- Confirm the signature matches — same code, same operation class.
- Present the cause + the documented fix + the reference URL. Flag whether the fix is read-only (a config check) or a change that needs approval.
- Route out if there is no exact match: generic AKS incidents →
aks-troubleshooting; non-AKS failures → no AKS skill. A bareVMExtensionProvisioningErrororAllocationFailedis not enough to diagnose. A numeric exit code also requires AKSvmssCSE/ CSE context. Request the nested error, complete message, operation, and AKS resource context.
What ships with it
1 file 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.
- 10d ago First seen · 53 lines · 242 tokens per session scan A 5ea1438388f9
aks-known-issues is a skill published in the GitHub repository Azure/AKS-Skills (4 stars, last pushed today), licensed MIT. It adds 242 tokens to every session and 2,666 once invoked, about $0.0012 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-31.
Other skills, from other repositories
azure-kubernetes-automatic-readiness
Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic…
azure-diagnostics
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, VM RDP, Linux SSH, VM black…
datadog-ninja
Master orchestrator for 57 official Datadog agent skills from DataDog/pup and datadog-labs/agent-skills. Use when working with ANY Datadog observability task: APM and distributed tracing, log search and pipelines, monitors and alerting, live production debugging, audit trail investigations, browser SDK…
azure-ninja
Master orchestrator for 40 Azure agent skills from Microsoft official and community repositories. Use when working with ANY Azure service, architecture, deployment, operations, security, cost optimization, diagnostics, or development task. Routes to the optimal specialized skill based on context. Triggers: Azure…
alibaba-observability-incident-responder
Respond to Alibaba Cloud incidents using CloudMonitor alarms, SLS log analytics, ARMS APM distributed tracing, and alert governance for ECS, RDS, ACK, and network services.
azure-resource-health-incident-triage
Use this skill for Azure Resource Health, Service Health, activity-log alert, and first-pass incident triage when the question is whether Azure platform health is part of the problem.