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 gke-labs/kube-agents --skill gke-upgradesgit clone --depth 1 https://github.com/gke-labs/kube-agentsWrote 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/gke-labs/kube-agents/gke-upgrades)<a href="https://agentmods.dev/skills/gke-labs/kube-agents/gke-upgrades"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/gke-upgrades/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/gke-labs/kube-agents/gke-upgrades"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/gke-upgrades.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00202 | $0.06420 |
| Opus 5.5 | $0.00081 | $0.02568 |
| Sonnet 5.5 | $0.00040 | $0.01284 |
| Haiku 4.5 | $0.00020 | $0.00642 |
Grade A, and why
gke-upgrades 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 4d 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GKE Upgrades & Maintenance
Produce clear, actionable documents — upgrade plans, runbooks, or checklists — tailored to the user's environment. Output should be specific to their cluster mode, release channel, version, and workload types rather than generic advice.
Always frame guidance around the auto-upgrade model: auto-upgrade with maintenance windows and exclusions is the preferred control mechanism.
A change goes out as a pull request to the GitOps repository, never as a write from here: Kubernetes objects as YAML through
gke-manifest-generation, cluster settings and other Google Cloud resources as Config Connector YAML throughgcp-config-connector, opened withsubmit-suggestion. Each profile's config offers only thegkeMCP server's read tools, and the broker refuseskubectlandgcloudwrites. A control-plane upgrade reaches the cluster as a pull request changing the version floor or release-channel field (spec.minMasterVersionorspec.releaseChannel.channelon theContainerCluster). A node-pool version change (an upgrade, a downgrade or rollback, or resuming a stopped upgrade) is an operation, not desired state: write the exactgcloud container clusters upgrade CLUSTER_NAME --node-pool NODE_POOL_NAME --cluster-version VERSION --location LOCATIONcommand as a step for the platform operator to run, not one to run from here, and never proposespec.versionon aContainerNodePool. A pool on a release channel cannot turn auto-upgrade off, so a version pinned in the repository fights it: Config Connector moves the pool back to the pin after each automatic upgrade, re-rolling its nodes, and a rollback pin holds the pool at the old version indefinitely. The pool's upgrade strategy (spec.upgradeSettings) is desired state and stays a pull request.
Context Gathering
Before producing any upgrade artifact, establish:
- Cluster mode — Standard or Autopilot? (Autopilot has no node pool management, mandatory resource requests, no SSH)
- Current and target versions — Node version skew must be within 2 minor versions of control plane.
- Release channel — Rapid, Regular, Stable, or Extended.
- Environment topology & Rollout Sequencing — Single vs multi-cluster, dev/staging/prod tiers, and whether Rollout Sequencing is used.
- Workload sensitivity — StatefulSets, databases, GPU, long-running batch need special handling.
What ships with it
3 files 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.
- 4d ago Changed · +38 lines 29c87f76e78d
- 5d ago Changed · +1 lines 528122cb8105
- 7d ago Changed e85271c11f98
- 8d ago Changed · +2 lines 8dbe8a43406d
- 11d ago Changed 9ddd64e6c08a
- 12d ago Changed · +4 lines de1ed924ded0
- 13d ago Changed · +7 lines 5d39fe7a8aba
- 18d ago Changed · +4 lines af31dff51f3c
- 1mo ago Changed · +5 lines 415648402870
- 1mo ago First seen · 244 lines · 202 tokens per session scan A cb43e72b98ba
gke-upgrades is a skill published in the GitHub repository gke-labs/kube-agents (116 stars, last pushed today), licensed Apache-2.0. It adds 202 tokens to every session and 6,420 once invoked, about $0.0008 per session on Opus 5.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-09-03.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".