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.00034 | $0.01052 |
| Opus 5 | $0.00017 | $0.00526 |
| Sonnet 5 | $0.00007 | $0.00210 |
| Haiku 4.5 | $0.00003 | $0.00105 |
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 4d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Cloud gcloud CLI AI Skill Guide
Overview
gcloud is the primary CLI for Google Cloud Platform. It authenticates against GCP Identity, scopes work to a project, and drives APIs for Compute Engine, GKE, Cloud Run, Cloud Storage, IAM, and logging. Agents should treat project ID, region, and account as first-class context - most "wrong resource" bugs are wrong active config, not wrong YAML.
+------------------+ +-------------------+ +--------------------+
| gcloud config | --> | Cloud APIs / IAM | --> | GCE / GKE / Run |
| account+project | | Resource Manager | | GCS / Artifact Reg |
+------------------+ +-------------------+ +--------------------+
When to use
- Creating or switching GCP projects, regions, and named configurations
- Deploying to Cloud Run or inspecting GKE clusters with
gcloud+kubectl - Managing GCS buckets, Artifact Registry images, and service accounts
- Diagnosing auth failures (
Reauthentication required, permission denied)
Operational directives
- Always print active context first:
gcloud config listandgcloud auth list. - Prefer named configurations (
gcloud config configurations create) over silently mutating the default. - Use
--projectand--regionflags on mutating commands; do not rely on ambient defaults in scripts. - Prefer least-privilege service accounts; never embed user refresh tokens in CI.
- Prefer
--format=jsonor--format=yamlfor machine parsing; never scrape human tables in automation.
Concrete examples
Context and auth
gcloud auth login
gcloud config set project my-prod-123
gcloud config set compute/region us-central1
gcloud config configurations create staging
gcloud config configurations activate staging
gcloud config list
Cloud Run deploy (source)
gcloud run deploy api \
--source=. \
--region=us-central1 \
--allow-unauthenticated=false \
--service-account=api-runtime@my-prod-123.iam.gserviceaccount.com \
--set-env-vars=LOG_LEVEL=info
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.
- 4d 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 (1 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,052 once invoked, about $0.0002 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-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…
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.
cloud-run-basics
Cloud Run expert guidance. Use when deploying services, running jobs, or managing worker pools for HTTP, scheduled tasks, or background processing.
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.