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 gcp-config-connectorgit 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/gcp-config-connector)<a href="https://agentmods.dev/skills/gke-labs/kube-agents/gcp-config-connector"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/gcp-config-connector/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/gcp-config-connector"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/gcp-config-connector.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.00150 | $0.03405 |
| Opus 5.5 | $0.00060 | $0.01362 |
| Sonnet 5.5 | $0.00030 | $0.00681 |
| Haiku 4.5 | $0.00015 | $0.00341 |
Grade A, and why
gcp-config-connector 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 6d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Connector (KCC) Authoring
On a repository that keeps its Google Cloud resources as Config Connector
YAML, a change leaves this agent as a manifest in the GitOps repository,
reviewed by a human and applied by the customer's reconciler (a repository
that keeps them as Terraform gets the gcp-terraform skill instead). This skill writes that manifest. It reads the cluster
and the cloud project to decide what to write, validates the result against
the CRDs the customer actually runs, and opens the pull request through
submit-suggestion. Nothing here mutates a cluster or a project, and the
command policy refuses the verbs that would.
When to Use
- A new GKE cluster or node pool, or a change to one — create a cluster
someone asked for, grow or shrink a pool, turn on autoscaling, change a
release channel or maintenance window, adopt a cluster the repo does not
yet describe. A new cluster is a create like any other: this skill, not a
gcloudorgkeMCP create, is how it reaches the project. - A Cloud SQL change — add a read replica, change a tier, enable backups or high availability.
- A VPC firewall rule — open or close a port, narrow a source range, disable a rule, turn on logging.
- Adopting a resource that exists in Google Cloud but has no manifest in the repository (acquisition).
When NOT to Use
- Kubernetes workloads (Deployments, Services, NetworkPolicies): the
gke-manifest-generationskill. - A repository whose
provisioning/holds Terraform HCL rather than KCC YAML: thegcp-terraformskill. This skill authors KRM only. - Kinds outside the families catalogued in
references/. Other Config Connector kinds follow the same annotations and workflow, but their immutable fields are not catalogued here; validate every field withkubectl explainand say in the PR body that the kind is outside the catalogued set. - Fixing a fleet-audit finding: the
fleet-auditskill opens that PR.
What ships with it
4 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.
- 6d ago Changed · +2 lines · +6 tokens per session 40a4809c00fc
- 8d ago Changed · +2 lines · -8 tokens per session f9c188e10bc0
- 26d ago Changed 288ba757ac00
- 29d ago Changed · -5 lines 75060d9d7b81
- 1mo ago First seen · 270 lines · 152 tokens per session scan A 7972f0b0c33c
gcp-config-connector is a skill published in the GitHub repository gke-labs/kube-agents (116 stars, last pushed today), licensed Apache-2.0. It adds 150 tokens to every session and 3,405 once invoked, about $0.0006 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".