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-load-bearing-changegit 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-load-bearing-change)<a href="https://agentmods.dev/skills/gke-labs/kube-agents/gke-load-bearing-change"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/gke-load-bearing-change/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-load-bearing-change"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/gke-load-bearing-change.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.00071 | $0.03400 |
| Opus 5.5 | $0.00028 | $0.01360 |
| Sonnet 5.5 | $0.00014 | $0.00680 |
| Haiku 4.5 | $0.00007 | $0.00340 |
Grade B, and why
gke-load-bearing-change scanned grade B with 1 finding 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| A pod-template field (securityContext, capabilities, user) | A retired ReplicaSet still carrying the declared value; kubelet refusals on the pods it made (`container has runAsNonRoot and image will run as root`, surfac How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GKE Load-Bearing Change
Use this skill when something changed a live object outside git and you have to say whether the declared state or the live state should win. It answers one question, and that question decides the recommendation: would the state git declares still run if you put it back? A change that is the only reason a workload is up is load-bearing, and proposing to revert it proposes an outage. A change that nothing depends on is not, and proposing to codify it writes somebody's accident into git.
The skill is read-only: it reads history, events, the live object and whatever depends on it, and proposes nothing beyond naming what it found.
It does not try to learn why the change was made. An operator unblocking a deploy at speed leaves no annotation and no ticket, so the motive is usually unknowable, and guessing at one is how a report ends up asserting something it cannot support. Load-bearing is a property of the cluster, not of anybody's intent, and it is observable.
When to run it
- A drift card asks you to choose between reverting an out-of-band change and codifying it.
- Any time the recommendation you are about to write is "put it back the way the manifests say", and the manifests have not been applied successfully since the change.
- A limit, a probe, a replica count, a policy or a hardening setting is looser or absent in the cluster compared with git, and the workload is healthy. Health under the changed state is the first hint that the change is doing something.
Skip it when the live object already matches the declared state: a GitOps controller reconciled the change away and there is nothing left to decide.
The method
Four steps, and they do not depend on what kind of object changed. Step 3 is where the evidence location varies, and the table below is for that step.
1. Establish what the revert would actually put back. Not the one field the card names — the whole declared state as it would land. Two fields are often taken together (a runAsNonRoot and the runAsUser beside it), and a revert that restores one without the other produces a third state nobody has ever run.
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.
- 5d ago First seen · 130 lines · 71 tokens per session scan B d6d18a247e02
gke-load-bearing-change is a skill published in the GitHub repository gke-labs/kube-agents (109 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 3,400 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-17.
Other skills, from other repositories
gke-workload-troubleshooting
Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.
gke-workload-scaling-troubleshooting
Diagnoses GKE HorizontalPodAutoscaler (HPA) failures — metrics showing as , FailedGetResourceMetric / FailedGetScale / FailedComputeMetricsReplicas events, missing Pod resource requests, custom/external metrics-pipeline breakage (FailedGetExternalMetric / FailedGetCustomMetric, unavailable metrics adapter…
gke-ai-troubleshooting-tpu-mxla-hang
Diagnose GKE Cloud TPU multi-slice training hangs (Megascale HANGDETECTED logs and hang monitored events) using the ML Diagnostics Megascale XLA (MXLA) Hang Analyzer (gcloud alpha mldiagnostics monitored-events) and 1-minute Cloud Monitoring multi-slice latency metrics (kubernetes.io/container/multislice/).…
gke-ai-troubleshooting-tpu-performance-degradation
Diagnose GKE Cloud TPU training throughput drops and step-time regressions (15%+ TPU duty-cycle drop) using ML Diagnostics Workload Monitoring (gcloud alpha mldiagnostics monitored-events / hypercomputecluster.googleapis.com/v1alpha) and 1-minute Cloud Monitoring system metrics (kubernetes.io/node/accelerator/).…
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…