What is google-cloud-operations?

A command-line workflow for managing Google Cloud accounts, projects, permissions, APIs, billing settings, logs, and audit records with gcloud. It requires the active identity and project scope to be checked before consequential operations.

Use it for bounded Google Cloud administration outside application deployment. It helps inspect configurations, IAM access, enabled APIs, billing context, logs, and audit information.

It reduces the chance of changing the wrong Google Cloud project, account, or billing context. It also makes the effective credentials and scope visible before access or configuration changes.

google-cloud-operations — Skill for Claude Code and Codex by fmind

Install

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.

Any agent

npx skills add fmind/dotfiles --skill google-cloud-operations

Clone the repo

git clone --depth 1 https://github.com/fmind/dotfiles

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/fmind/dotfiles/google-cloud-operations/github.svg)](https://agentmods.dev/skills/fmind/dotfiles/google-cloud-operations)

Your own site

<a href="https://agentmods.dev/skills/fmind/dotfiles/google-cloud-operations"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/google-cloud-operations/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/fmind/dotfiles/google-cloud-operations"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/google-cloud-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 708 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00708
Opus 5.5	$0.00014	$0.00283
Sonnet 5.5	$0.00007	$0.00142
Haiku 4.5	$0.00003	$0.00071

Measured 1mo ago against content hash baaa324c3722, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

google-cloud-operations 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.

skills/google-cloud-operations/SKILL.md · 41 lines

How it starts

The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Operate Google Cloud

Use gcloud for bounded account, project, IAM, API, billing, logging, and audit operations. Use cloud-run for application deployment, terraform-stack for provisioned infrastructure, and incident-response for a live outage.

Workflow

Resolve identity and scope: Inspect the active named configuration, account, project, and quota or billing project. Do not activate another configuration or change defaults merely to make a command work.

gcloud config configurations list --format=json
gcloud config configurations describe <configuration> --format=json
gcloud config get auth/impersonate_service_account --configuration <configuration>
gcloud config get auth/access_token_file --configuration <configuration>
gcloud projects describe <project-id> --format=json

Resolve the effective principal: Check CLOUDSDK_AUTH_IMPERSONATE_SERVICE_ACCOUNT, CLOUDSDK_AUTH_ACCESS_TOKEN_FILE, and invocation flags as well as the named configuration. Impersonation and access-token-file overrides replace the selected account; before consequential calls, pin the intended impersonation chain explicitly or prove that neither override is active.
Pin every consequential call: Pass --configuration, --account, --project, and --billing-project when applicable so terminal defaults cannot redirect the operation. Pass --impersonate-service-account when the approved effective principal is an impersonation chain. Prefer a named configuration per environment.
Start read-only: Describe the resource, current IAM policy, enabled services, billing linkage, relevant logs, quotas, and dependencies. Bound list and log queries by project, resource, and time window.
Plan the mutation: State the exact resource, before and after state, permissions, cost or quota impact, dependent services, rollback, and verification command. Enabling APIs, changing IAM or billing, deleting resources, and production operations require explicit authority.
Use short-lived identity: Prefer user OAuth, Workload Identity Federation, or explicit service-account impersonation over downloaded keys. Never print access tokens, credential files, or debug HTTP headers.
Apply minimally: Change only the named resource. --quiet suppresses prompts; it does not make an operation safe or authorize it.
Verify independently: Re-read the resource and its audit or operation status, then confirm behavior at the intended boundary. Separate local configuration, accepted API request, completed operation, and user-visible outcome.

Read the full file on GitHub · 41 lines

Changes

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 · 41 lines · 34 tokens per session scan A baaa324c3722

Subscribe to this mod's changes

google-cloud-operations is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 708 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-08-31.

Claude Code Cloud DevOps and cloud ai-agents chezmoi dotfiles fish-shell gemini-cli

google-cloud-operations

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Operate Google Cloud

Workflow

What this file has done since we first saw it

Other skills, from other repositories

observability

databricks

aws

kubernetes

gcloud

infra-as-code