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 agentmods add skills/microsoft/aks-lab-githubcopilot/aks-helmnpx skills add microsoft/AKS-Lab-GitHubCopilot --skill aks-helmgit clone --depth 1 https://github.com/microsoft/AKS-Lab-GitHubCopilotWhat 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 | $0.00000 | $0.00956 |
| Opus 5 | $0.00000 | $0.00478 |
| Sonnet 5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
aks-helm 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: AKS Helm Chart for the Orchestrator
Chart layout
infra/aks/helm/zavashop/
├── Chart.yaml
├── values.yaml
└── templates/
├── _helpers.tpl
├── serviceaccount.yaml
├── secretproviderclass.yaml
├── deployment.yaml
└── service.yaml
values.yaml shape
image:
repository: "" # acr.azurecr.io/zavashop/orchestrator
tag: "" # git short sha — REQUIRED, no default
pullPolicy: IfNotPresent
workloadIdentity:
clientId: "" # UAMI client id, REQUIRED
keyVault:
name: "" # REQUIRED
tenantId: "" # REQUIRED
a2a:
inventory: ""
supplier: ""
logistics: ""
pricing: ""
resources:
requests: { cpu: "200m", memory: "256Mi" }
limits: { cpu: "1", memory: "1Gi" }
podSecurityContext:
runAsNonRoot: true
runAsUser: 10001
runAsGroup: 10001
fsGroup: 10001
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: ["ALL"]
serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: orchestrator-sa
namespace: {{ .Release.Namespace }}
annotations:
azure.workload.identity/client-id: {{ required "workloadIdentity.clientId" .Values.workloadIdentity.clientId }}
labels:
azure.workload.identity/use: "true"
secretproviderclass.yaml
apiVersion: secrets-store.csi.x-k8s.io/v1
kind: SecretProviderClass
metadata:
name: zavashop-github-token
spec:
provider: azure
parameters:
usePodIdentity: "false"
useVMManagedIdentity: "false"
clientID: {{ .Values.workloadIdentity.clientId }}
keyvaultName: {{ .Values.keyVault.name }}
tenantId: {{ .Values.tenantId }}
objects: |
array:
- |
objectName: GITHUB-TOKEN
objectType: secret
secretObjects:
- secretName: github-token
type: Opaque
data:
- objectName: GITHUB-TOKEN
key: token
deployment.yaml essentials
metadata.labels.azure.workload.identity/use: "true"on the pod template.serviceAccountName: orchestrator-sa.topologySpreadConstraintsovertopology.kubernetes.io/zone,maxSkew: 1.- Non-root pod and container security contexts from
values.yaml. - Mount the CSI volume; project
GITHUB_TOKENenv viasecretKeyReftogithub-token/token. - Env:
AZURE_CLIENT_ID,ZAVA_COPILOT_MODEL=gpt-5.5,ZAVA_COPILOT_TIMEOUT_SECONDS=120, and four specialist A2A URLs from.Values.a2a.*. - Probes:
/healthz,/readyzon the orchestrator service port 8000 (see deploy-engineer rule 7).
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.
- yesterday First seen · 122 lines · 0 tokens per session scan A 81ee232d961c
aks-helm is a skill published in the GitHub repository microsoft/AKS-Lab-GitHubCopilot (7 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 956 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…