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 jpantsjoha/googlecloud-plugin --skill gkegit clone --depth 1 https://github.com/jpantsjoha/googlecloud-pluginWrote 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/jpantsjoha/googlecloud-plugin/gke)<a href="https://agentmods.dev/skills/jpantsjoha/googlecloud-plugin/gke"><img src="https://agentmods.dev/badge/skills/jpantsjoha/googlecloud-plugin/gke/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/jpantsjoha/googlecloud-plugin/gke"><img src="https://agentmods.dev/badge/skills/jpantsjoha/googlecloud-plugin/gke.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.00090 | $0.00706 |
| Opus 5.5 | $0.00036 | $0.00282 |
| Sonnet 5.5 | $0.00018 | $0.00141 |
| Haiku 4.5 | $0.00009 | $0.00071 |
Grade A, and why
gke 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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GKE — Google Kubernetes Engine
Run Kubernetes workloads with Google's managed control plane. Choose Autopilot (fully managed nodes) or Standard (you manage node pools).
Mode Selection
| Autopilot | Standard | |
|---|---|---|
| Node management | You | |
| Billing | Per pod resource | Per node |
| Best for | Ops-light teams, variable load | Fine-grained node control |
Core Patterns
Create an Autopilot cluster (recommended)
# Billable action — GKE charges per cluster + node resources
gcloud container clusters create-auto CLUSTER_NAME \
--region REGION \
--project PROJECT_ID
Get credentials
gcloud container clusters get-credentials CLUSTER_NAME \
--region REGION \
--project PROJECT_ID
Workload Identity (never use SA key files in pods)
# Annotate the Kubernetes SA to impersonate a GCP SA
kubectl annotate serviceaccount KSA_NAME \
iam.gke.io/gcp-service-account=GSA_EMAIL
# Bind the GCP SA
gcloud iam service-accounts add-iam-policy-binding GSA_EMAIL \
--role roles/iam.workloadIdentityUser \
--member "serviceAccount:PROJECT_ID.svc.id.goog[NAMESPACE/KSA_NAME]"
Safety Rules
- Always use Workload Identity — never mount SA key files into pods
- Enable Binary Authorization for production clusters
- Cost warning: GKE clusters incur cluster management fee + node costs
References
What ships with it
1 file 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.
- 1mo ago First seen · 71 lines · 90 tokens per session scan A 2be34010924c
gke is a skill published in the GitHub repository jpantsjoha/googlecloud-plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 90 tokens to every session and 706 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
ak-cloud-deploy
Deploy an Agent Kernel project to AWS, Azure, or GCP using Terraform modules, or to any Kubernetes cluster (on-prem, baremetal, EKS) using the official Helm chart. Supports serverless and containerized modes for all three clouds. AWS supports execution modes (restsync, restasync, async, stream), queue-based scalable…
apify-actor-development
Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.
azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
apify-actorization
Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output.
aiq-deploy
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
dynamo-recipe-runner
Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.