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 agentmods add skills/fmind/dot/google-cloudnpx skills add fmind/dot --skill google-cloudgit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/google-cloud)<a href="https://agentmods.dev/skills/fmind/dot/google-cloud"><img src="https://agentmods.dev/badge/skills/fmind/dot/google-cloud.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00546 |
| Opus 5 | $0.00021 | $0.00273 |
| Sonnet 5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
google-cloud 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 yesterday.
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.
What it actually says
Google Cloud
Google Cloud is the default cloud for Fmind projects. gcloud owns CLI operations, cloud-run owns deployment, and terraform-stack owns provisioning; this skill maps a product area (compute, data, AI platform, GKE, operations, security, architecture) to the cloud group of the official catalog.
Gotchas
- Cloud Run first: GKE skills exist, but Kubernetes stays opt-in per k8s-local.
- Region and project:
europe-west1unless the project says otherwise, with account, project, and billing pinned per gcloud. - Authority: every installed skill drives
gcloudunder the hood, so mutations, API enablement, and spend still need explicit approval.
Official Skills
Upstream: google/skills (skills/cloud group; the CLI guardrail and authentication skills apply to almost every task, and deeper database and analytics skills live in the gemini-cli-extensions/* repositories its marketplace file lists). List the current release, then install what the task needs at project scope after reviewing the snapshot (see agent-skills):
skills add https://github.com/google/skills/tree/main/skills/cloud --list
skills add https://github.com/google/skills/tree/main/skills/cloud --skill <name> -y
Documentation
- Google Cloud documentation · google/skills
- Companion skills: gcloud, cloud-run, google-adk, terraform-stack, google-developer (any other Google product).
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.
- yesterday First seen · 35 lines · 42 tokens per session scan A b4ec3f1cf563
google-cloud is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 546 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-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.
python-script
Write standalone single-file Python scripts using PEP 723 inline metadata and uv. Use when creating a quick CLI script that needs dependencies without a full project.
dot-release
Prepare, tag, and push a versioned fmind/dotfiles release locally to trigger GitHub Actions CD publication.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.