Borrowing it
Nothing to install: this file belongs to gke-labs/kube-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gke-labs/kube-agents/main/.agents/skills/install-kube-agents/SKILL.mdgit 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/install-kube-agents)<a href="https://agentmods.dev/skills/gke-labs/kube-agents/install-kube-agents"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/install-kube-agents/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/install-kube-agents"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/install-kube-agents.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.00032 | $0.02776 |
| Opus 5 | $0.00016 | $0.01388 |
| Sonnet 5 | $0.00006 | $0.00555 |
| Haiku 4.5 | $0.00003 | $0.00278 |
Grade C, and why
install-kube-agents scanned grade C with 2 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 today.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/gke-labs/kube-agents/<RELEASE_VERSION>/install.sh | bash -s -- \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/gke-labs/kube-agents/<RELEASE_VERSION>/install.sh | bash -s -- \ How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
install-kube-agents Skill
This skill provides step-by-step instructions for AI Agents to non-interactively provision Google Cloud GKE infrastructure and deploy the kube-agents Platform Agent.
What install.sh actually does
It is a front-end, not a second provisioner. It loads install.env (the install's
hand-authored configuration), collects anything still missing, generates
terraform/examples/full-install/terraform.tfvars from the result, and then runs the composition's
lifecycle.sh apply — the Terraform root in
terraform/examples/full-install/ owns every
GCP resource and installs the Helm chart (charts/kube-agents) that owns every Kubernetes one.
Terraform state goes to a GCS bucket (<project>-kube-agents-tfstate, versioned, prefix
kube-agents/<cluster>), so uninstall.sh and upgrade.sh can find the install from a fresh
clone. The installer sources
scripts/installer/installer_common.sh before its
first prompt, so its defaults and accepted values are the ones defined there; that file is where a
default changes.
Order of operations: resolve the image/source ref → check CLI prerequisites (including
terraform, which it offers to install; make is not needed) → put the repository on disk and
verify it against that ref → load install.env → interview for what is missing → generate
terraform.tfvars → refuse a service account another install in the project owns
(check_service_account_ownership, before the summary and the dry-run exit) → run
lifecycle.sh apply. The source check happens before the interview, so a bad ref fails in
seconds rather than after a dozen answers. Some steps stay gcloud calls outside the apply — before
it, CMEK, the Workload Identity pool and NetworkPolicy enforcement on a pre-existing cluster; after
it, the managed-OTel scope on a cluster it created — and the GitHub App PEM import runs through
the Minty CLI so the key never enters Terraform state. Re-running the installer (or its --menu
Day-2 panel's Save & Apply) reconciles every change through one terraform apply.
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.
- today Changed · +7 lines 558718f89941
- yesterday Changed · +20 lines 5eae223ff405
- 7d ago Changed · +4 lines 6e95dd3ecb90
- 11d ago First seen · 140 lines · 32 tokens per session scan C 445621ef104f
install-kube-agents is a skill published in the GitHub repository gke-labs/kube-agents (53 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 2,776 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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-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 disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
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".
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
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…