Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/gke-labs/kube-agentsnpx agentmods add skills/gke-labs/kube-agents/manage-clusterWrote 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/manage-cluster)<a href="https://agentmods.dev/skills/gke-labs/kube-agents/manage-cluster"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/manage-cluster/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/manage-cluster"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/manage-cluster.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 30 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00053 | $0.00775 |
| Opus 5 | $0.00026 | $0.00387 |
| Sonnet 5 | $0.00011 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
manage-cluster 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 9d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Cluster Skill
When a user asks you to manage (onboard / start watching) a specific existing GKE cluster — e.g. "manage my cluster payments-prod in us-central1" — bring it under management by creating its Cluster Agent profile. After this, the cluster gets a per-cluster agent and is delegable via the kanban board.
This is the explicit, user-driven counterpart to onboarding-time creation (gke-cluster-creation). It is safe to run repeatedly (idempotent).
Steps
-
Gather the target. You need
project,cluster, andlocation.- Use any values the user gave. If the user omits the project, resolve it:
- default to the platform's active project:
gcloud config get-value project; then - confirm the cluster exists in that project (next step). If it isn't there, or the name is ambiguous, run
gcloud container clusters list --format="value(name,location,resourceLabels)"(optionally--project <p>) to locate it, and ask the user only if still ambiguous.
- default to the platform's active project:
- Use any values the user gave. If the user omits the project, resolve it:
-
Verify the cluster exists before creating a profile (clean error instead of a half-scaffold):
verify_gke_cluster(platform GKE tool) orgcloud container clusters describe <cluster> --location <location> --project <project> --format="value(status)".- If it does not exist, tell the user and stop.
-
Create the profile:
python3 /opt/data/scripts/cluster_agent_profile.py create \ --project "<project>" --cluster "<cluster>" --location "<location>"This scaffolds the Cluster Agent profile home on the data PVC, pins a read-only
KUBECONFIGto that cluster, stamps itscluster_identityinto the profile config, and prints the profile name. It is idempotent — re-managing an already-managed cluster is a safe no-op. -
Confirm to the user. Report that
<cluster>(<project>/<location>) is now managed: it has a Cluster Agent and is delegable (kanban).
This step gives the cluster an agent immediately. Even without it, the
cluster-agent-reconcilecron automatically gives every cluster in the project — including the management cluster where kube-agents runs — an agent on its next run; this skill just does it now.
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.
- 9d ago First seen · 47 lines · 53 tokens per session scan A dc399146ce78
manage-cluster is a skill published in the GitHub repository gke-labs/kube-agents (54 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 775 once invoked, about $0.0003 per session on Opus 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-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…
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".
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…