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/alivirgo/Major-AI-Skillsnpx agentmods add skills/alivirgo/major-ai-skills/gcloud-cliWrote 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/alivirgo/major-ai-skills/gcloud-cli)<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/gcloud-cli"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/gcloud-cli/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/alivirgo/major-ai-skills/gcloud-cli"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/gcloud-cli.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.00037 | $0.01938 |
| Opus 5.5 | $0.00015 | $0.00775 |
| Sonnet 5.5 | $0.00007 | $0.00388 |
| Haiku 4.5 | $0.00004 | $0.00194 |
Grade A, and why
gcloud-cli 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 2d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Cloud gcloud CLI AI Skill Guide (Claude)
Overview & Engine Architecture
gcloud authenticates a principal, scopes work to a project (and often region/zone), and drives Cloud APIs for Compute, GKE, Cloud Run, GCS, Artifact Registry, IAM, and logging. CLI auth (gcloud auth login) is distinct from Application Default Credentials (gcloud auth application-default login)—SDKs use ADC; the CLI uses its own login. Agents treat active configuration + project ID as first-class context: most “wrong resource” bugs are wrong config, not wrong YAML.
┌─────────────────────────────────────────────────────────────┐
│ gcloud auth & API path │
│ │
│ Principal │
│ ├── User: gcloud auth login │
│ ├── Impersonation: --impersonate-service-account │
│ ├── WIF: gcloud auth login --cred-file=… (CI / external) │
│ └── Metadata SA (GCE / Cloud Run / Cloud Build) │
│ │
│ Config │
│ ├── Named configurations (account + project + region) │
│ ├── ADC file (apps/SDKs only — not used by gcloud itself) │
│ └── Flags: --project / --region override ambient defaults │
│ │
│ APIs → GKE · Cloud Run · GCS · Artifact Registry · IAM │
└─────────────────────────────────────────────────────────────┘
When to use / when not to
Use when
- Switching projects/regions via named configurations; deploying Cloud Run; wiring GKE credentials.
- Managing GCS, Artifact Registry, and IAM bindings with least privilege.
- Diagnosing auth: reauth required, WIF, ADC vs CLI confusion.
Do not use when
- Full multi-env topology belongs in IaC →
@terraform/@pulumi. - Day-2 cluster workloads after kubeconfig →
@kubernetes. - Someone asks to commit a service account JSON key → refuse; use WIF, impersonation, or attached SA /
@vault.
What ships with it
2 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.
- 2d ago Changed · +65 lines · +6 tokens per session aa7bd0215bcf
- 1mo ago Changed · -3 tokens per session b1b29e5ab13e
- 1mo ago First seen · 109 lines · 34 tokens per session scan A 14dfc3ae4a24
gcloud-cli is a skill published in the GitHub repository alivirgo/Major-AI-Skills (2 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,938 once invoked, about $0.0001 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-05.
Other skills, from other repositories
gcp-essentials
Use when running a small product on core Google Cloud via the gcloud CLI: a project, Cloud Run deploys, a locked-down Cloud Storage bucket, managed Cloud SQL, and least-privilege IAM wiring them together. NOT AWS (that is aws-essentials), NOT the CI pipeline that ships the image (that is deployment), NOT Postgres…
cloud-run-basics
Cloud Run expert guidance. Use when deploying services, running jobs, or managing worker pools for HTTP, scheduled tasks, or background processing.
gcloud
Guidance for using the Google Cloud CLI, a command-line tool for managing Google Cloud resources. It covers login, projects, regions, virtual machines, disks, and remote command execution.
gcp-cloud-run
Production-ready Cloud Run on GCP: containerized services, Cloud Run Functions, cold start optimization, Pub/Sub integration, Cloud SQL, Secret Manager, concurrency tuning. Covers sharp edges and gotchas.
implementing-gcp-binary-authorization
Implement GCP Binary Authorization to enforce deploy-time security controls that ensure only trusted, attested container images are deployed to Google Kubernetes Engine and Cloud Run.
auditing-gcp-iam-permissions
Auditing Google Cloud Platform IAM permissions to identify overly permissive bindings, primitive role usage, service account key proliferation, and cross-project access risks using gcloud CLI, Policy Analyzer, and IAM Recommender.