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/fmind/dotfilesnpx agentmods add skills/fmind/dotfiles/cloud-runWrote 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/dotfiles/cloud-run)<a href="https://agentmods.dev/skills/fmind/dotfiles/cloud-run"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/cloud-run/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/fmind/dotfiles/cloud-run"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/cloud-run.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.00028 | $0.01703 |
| Opus 5.5 | $0.00011 | $0.00681 |
| Sonnet 5.5 | $0.00006 | $0.00341 |
| Haiku 4.5 | $0.00003 | $0.00170 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Run Deployment Standard
Canonical path from a container image to a running GCP service: Cloud Run is the default deploy target for web apps, APIs, and ADK agents — serverless containers, scale-to-zero, per-request billing. The image comes from the containerize skill (ko for Go, Dockerfile for Python); this skill covers registry, identity, deploy, and CD.
1. Deployment Ladder
gcloud run deploy(default): one command, ideal for a single service iterated from the CLI.- Declarative manifest: service.yaml applied with
gcloud run services replace— reviewable in PRs once settings accumulate (scaling, secrets, resources). - Full IaC:
google_cloud_run_v2_servicein the terraform-stack skill — when the service is one resource among many (domains, IAM, schedulers).
2. One-Time Project Setup
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
- Runtime identity: always deploy with a dedicated service account; grant it only what the app reads (e.g.
roles/secretmanager.secretAccessoron specific secrets) — never run on the default compute SA. - CI identity (keyless): create a Workload Identity Federation pool + provider once per project, then a deployer SA that GitHub Actions impersonates via OIDC — no exported keys:
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.
- 1mo ago First seen · 95 lines · 28 tokens per session scan A 0527a54710c6
cloud-run is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,703 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.
Other skills, from other repositories
kubernetes
Operate Kubernetes with kubectl, Helm, k9s, kustomize, and stern.
observability
Instrument Python services and agents: structlog logs, OpenTelemetry traces and metrics.
databricks
Operate Databricks bundles, jobs, pipelines, and Unity Catalog.
airflow
Develop and test Airflow DAGs with the Astronomer astro CLI.
aws
Operate AWS accounts and SSO profiles with aws and aws-sso-util.
docker
Run Docker, Compose, and Colima; build, scan, sign, and verify Python images.