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 fleet-upgrade-verificationgit 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/fleet-upgrade-verification)<a href="https://agentmods.dev/skills/gke-labs/kube-agents/fleet-upgrade-verification"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/fleet-upgrade-verification/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/fleet-upgrade-verification"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/fleet-upgrade-verification.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.00280 | $0.09565 |
| Opus 5.5 | $0.00112 | $0.03826 |
| Sonnet 5.5 | $0.00056 | $0.01913 |
| Haiku 4.5 | $0.00028 | $0.00957 |
Grade A, and why
fleet-upgrade-verification 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 — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet upgrade verification
Answer "against version X, which clusters lag, by how much, and is it the control plane or a node
pool" with a table read from the fleet, not from memory, and "which manifests in our GitOps
repositories declare an API that version X removes" with a scan read from Git. Use it when a user
asks whether an upgrade has reached every cluster, which members are behind a target, how far the
fleet is from a release-channel default, whether one cluster's control plane is current for its
channel (--cluster <location>/<name>), or whether the repositories are ready for a target
version. Run the version report again during a rollout and it also says, per member, what changed
since the previous run and which members have stopped moving (see "Track a rollout across runs" and references/track-a-rollout.md).
With --readiness it also says, per member, what would stop the upgrade: a PodDisruptionBudget
that blocks every node drain, a fail-closed admission webhook with an unreachable backend in the
upgrade's path or able to refuse the control plane's bootstrap RBAC writes (ClusterRoles and
ClusterRoleBindings; Roles and RoleBindings in kube-system and kube-public), a maintenance
exclusion or window, node pools too far below the target, or a blocker one of the per-entry rules
of the upgrade-failure catalogue files, and, as risks that do not block, what those rules name to
watch, a zonal control plane among them (see "Check upgrade readiness"). For upgrade plans,
runbooks and checklists, use the
gke-upgrades skill; it links back here when the question is one these two scripts answer.
"Version skew" here is the gap between a member's versions and the target. It is not configuration drift: the fleet-consistency audit compares a cluster's configuration against its live peers, and the drift-detection design (not yet shipped) means live state diverging from Git. Neither reads versions against a target.
Before you run anything: is this the brief?
A request for the upgrade readiness brief, for which findings need a decision, or for
this week's upgrade readiness report is not answered by this skill's table. Stop here, load the
upgrade-readiness-brief skill (skill_view upgrade-readiness-brief) and follow it: it reads the
Saturday review's copy under /opt/data/upgrade-readiness/weekly/ and the findings queue, and
answers in the brief's shape, which opens with Decide now and the undecided critical findings'
queue ids. Run this skill's report only when that skill tells you to (no weekly review exists yet),
or when the question is the readiness table itself ("is every cluster ready", "what would stop the
upgrade", "which clusters lag").
What ships with it
56 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.
- references/readiness-rules.md 31 KB
- references/track-a-rollout.md 3.8 KB
- scripts/api_deprecation_scan.py 35 KB runs code
- scripts/fleet_upgrade_report.py 111 KB runs code
- scripts/known_issues.json 29 KB
- scripts/readiness_rules/__init__.py 72 KB runs code
- scripts/readiness_rules/audit_log.py 44 KB runs code
- scripts/readiness_rules/capacity.py 36 KB runs code
- scripts/readiness_rules/cgroup_v2_runtime.py 7.2 KB runs code
- scripts/readiness_rules/changed_defaults.py 11 KB runs code
- scripts/readiness_rules/client_addon_skew.py 14 KB runs code
- scripts/readiness_rules/cluster_status_age.py 16 KB runs code
- scripts/readiness_rules/container_runtime.py 9.4 KB runs code
- scripts/readiness_rules/control_plane_upgrade_history.py 16 KB runs code
- scripts/readiness_rules/dataplane.py 5.9 KB runs code
- scripts/readiness_rules/deprecated_api_callers.py 4.9 KB runs code
- scripts/readiness_rules/finding.py 1.8 KB runs code
- scripts/readiness_rules/gpu_driver_mismatch.py 18 KB runs code
- scripts/readiness_rules/group_oom_kill.py 8.5 KB runs code
- scripts/readiness_rules/intree_volumes.py 8.0 KB runs code
- scripts/readiness_rules/known_issues_matrix.py 21 KB runs code
- scripts/readiness_rules/lb_connection_draining.py 10 KB runs code
- scripts/readiness_rules/node_image_coupled_agent.py 4.3 KB runs code
- scripts/readiness_rules/node_local_state.py 9.0 KB runs code
- scripts/readiness_rules/orphan_node_objects.py 7.1 KB runs code
- scripts/readiness_rules/removed_api_callers.py 8.8 KB runs code
- scripts/readiness_rules/removed_node_label.py 12 KB runs code
- scripts/readiness_rules/retired_registry.py 3.4 KB runs code
- scripts/readiness_rules/rollout_sequence_precheck.py 14 KB runs code
- scripts/readiness_rules/target_patch_valid.py 15 KB runs code
- scripts/readiness_rules/zonal_control_plane.py 2.4 KB runs code
- scripts/removed_apis.json 6.9 KB
- scripts/test_api_deprecation_scan.py 36 KB runs code
- scripts/test_audit_log.py 30 KB runs code
- scripts/test_audit_rules.py 41 KB runs code
- scripts/test_fleet_upgrade_report.py 173 KB runs code
- scripts/test_incident_replays.py 27 KB runs code
- scripts/test_readiness_rules_workloads.py 62 KB runs code
- scripts/test_readiness_rules.py 141 KB runs code
- scripts/test_rule_capacity.py 42 KB runs code
- scripts/test_rule_container_runtime.py 10 KB runs code
- scripts/test_rule_dataplane.py 5.7 KB runs code
- scripts/test_rule_intree_volumes.py 9.0 KB runs code
- scripts/test_rule_rollout_sequence_precheck.py 16 KB runs code
- scripts/test_upgrade_readiness.py 144 KB runs code
- scripts/testdata/addons_seeded_b.json 32 KB
- scripts/testdata/audit_log_sample.json 8.9 KB
- scripts/testdata/cluster_seeded_b.json 1.3 KB
- scripts/testdata/nodes_seeded_b.json 5.3 KB
- scripts/testdata/project_backend_services.json 1.2 KB
- scripts/testdata/project_instances.json 3.5 KB
- scripts/testdata/project_operations.json 13 KB
- scripts/testdata/rollout_sequences_list.json 928 B
- scripts/testdata/server_config_us_central1_a.json 3.7 KB
- scripts/upgrade_readiness.py 94 KB runs code
- scripts/upgrade_shape_tables.py 35 KB runs code
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 Changed · -2 lines de75f793557c
- 4d ago Changed · +11 lines 8762ef424f64
- 5d ago Changed · -5 lines 57b481bf6a36
- 6d ago Changed · -13 lines 6a9867b079f8
- 7d ago Changed · +33 lines · +13 tokens per session 90ca3801978a
- 8d ago Changed · +1 lines 6c1dc3aa80e3
- 11d ago Changed · -1 lines a5ae3814e43d
- 12d ago Changed · +66 lines · +48 tokens per session 1ba303101b5f
- 13d ago Changed · +97 lines · +47 tokens per session d5c0447f2ca2
- 14d ago First seen · 281 lines · 172 tokens per session scan A 0b86f61933c8
fleet-upgrade-verification is a skill published in the GitHub repository gke-labs/kube-agents (116 stars, last pushed today), licensed Apache-2.0. It adds 280 tokens to every session and 9,565 once invoked, about $0.0011 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-12.
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".