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/cloud-runnpx skills add fmind/dot --skill cloud-rungit 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/cloud-run)<a href="https://agentmods.dev/skills/fmind/dot/cloud-run"><img src="https://agentmods.dev/badge/skills/fmind/dot/cloud-run.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.00039 | $0.01420 |
| Opus 5 | $0.00019 | $0.00710 |
| Sonnet 5 | $0.00008 | $0.00284 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
cloud-run 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Run Deployment
Cloud Run is the default deploy target for web apps, APIs, and agents: serverless containers, scale-to-zero, per-request billing. containerize builds the image (ko for Go, Dockerfile for Python); this skill owns the registry, identities, deploy command, configuration, and CD job.
Workflow
-
Pick the tier:
gcloud run deployfor one service; service.yaml viagcloud run services replaceonce settings accumulate; terraform-stack for a fleet. -
Set up the project once: enable the APIs, create the Artifact Registry repository, and create a dedicated runtime service account (never the default compute SA; grant it only what the app reads).
gcloud services enable run.googleapis.com artifactregistry.googleapis.com iamcredentials.googleapis.com gcloud artifacts repositories create <slug> --repository-format=docker --location=<region> gcloud iam service-accounts create <slug>-runtime # runtime identity, least privilege -
Create the keyless CI identity: one Workload Identity Federation pool and provider per project, plus a deployer service account that GitHub Actions impersonates over OIDC, so no key is ever exported.
gcloud iam workload-identity-pools create github --location=global gcloud iam workload-identity-pools providers create-oidc github-actions \ --location=global --workload-identity-pool=github \ --issuer-uri="https://token.actions.githubusercontent.com" \ --attribute-mapping="google.subject=assertion.sub,attribute.repository=assertion.repository" \ --attribute-condition="assertion.repository_owner=='<owner>'" gcloud iam service-accounts create <slug>-deployer gcloud iam service-accounts add-iam-policy-binding "<slug>-deployer@<project>.iam.gserviceaccount.com" \ --role=roles/iam.workloadIdentityUser \ --member="principalSet://iam.googleapis.com/projects/<project_number>/locations/global/workloadIdentityPools/github/attribute.repository/<owner>/<repo>"
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.
- yesterday First seen · 87 lines · 39 tokens per session scan A ffac549742e6
cloud-run is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,420 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
cloud-run
Deploy container services to Google Cloud Run with Artifact Registry, keyless CI identity, Secret Manager, ko, or Dockerfiles.
google-cloud-operations
Operate Google Cloud with gcloud: pin account, configuration, project, and billing context for IAM, APIs, logs, and audits outside deployment.
terraform-stack
Canonical infrastructure-as-code stack — OpenTofu-first with tflint, trivy config scans, terraform-docs, native tests, and GCS state. Use for any Terraform or OpenTofu work.
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.
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.