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/robium-ai/robium/cloud-runnpx skills add robium-ai/robium --skill cloud-rungit clone --depth 1 https://github.com/robium-ai/robiumWhat 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.00225 | $0.04635 |
| Opus 5 | $0.00112 | $0.02318 |
| Sonnet 5 | $0.00045 | $0.00927 |
| Haiku 4.5 | $0.00022 | $0.00464 |
Grade A, and why
cloud-run scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
probing a boot by hand from a shell, *hold the connection* (`curl -N --http1.1 This is a copy
97% identical to cloud-run — 88 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cloud-run
The deploy target for robium's headless robotics and demo containers: a sim + bridge (or a policy server) built into an image, pushed to Artifact Registry, and run on Google Cloud Run so a browser can reach it, optionally one private instance per visitor, scale-to-zero when idle. This skill consolidates the Cloud-Run-specific mechanics and the robotics/headless gotchas that were hard-won deploying a Gazebo Harmonic + Nav2 stack (robium's nav-trial demo, 2026-07-12/13). It stays thin on general gcloud/GCP usage (that lives in Google's own docs) and embeds only what a robotics container hits that a plain web service never does.
When to use this skill
- Building and deploying any headless robotics/sim/demo container to Cloud Run:
the
gcloud/ Cloud Build → Artifact Registry →gcloud run deploypath, and the flag set a sim workload needs (CPU/memory, timeout, concurrency, affinity). - Debugging a robotics container that runs locally but misbehaves on Cloud Run: gz/DDS discovery silent (no multicast), sim boot freezes (CPU throttled between requests), WebSocket drops, affinity cookie ignored, deploy fails on VPC IPs.
- Wiring deploy auth from CI/servers with a GCP service-account key.
- The trigger phrases in the description: 'deploy to Cloud Run', 'gcloud run deploy', 'Cloud Build', 'Artifact Registry', 'session affinity', '--no-cpu-throttling', 'GZ_RELAY on Cloud Run', 'Cloud Run WebSocket timeout'.
- Cross-references: go to the sibling skill instead when the question is:
- The demo orchestrator, session gateway (claim/status/shutdown + ws tunnel),
mission-control page, or viewer handoff →
live-demo(it uses this skill's deploy mechanics but owns everything demo-shaped above the container). - Whether to use uv vs Docker, local↔remote reproducibility, or GPU
passthrough →
environments. - RunPod GPU inventory, provisioning, storage, proxy, diagnostics, billing,
or cleanup →
runpod. foxglove_bridgemechanics, thefoxglove.sdk.v1subprotocol, MCAP → thefoxgloveskill (this skill only covers reaching the bridge through Cloud Run's proxy).- The whole-stack decision and where deploy sits →
architect(routes here).
- The demo orchestrator, session gateway (claim/status/shutdown + ws tunnel),
mission-control page, or viewer handoff →
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.
- 2d ago First seen · 297 lines · 225 tokens per session scan A 4266e5c74612
cloud-run is a skill published in the GitHub repository robium-ai/robium (9 stars, last pushed 4d ago), licensed MIT. It adds 225 tokens to every session and 4,635 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 97% identical to cloud-run, differing in 88 lines, and is treated as a copy.
Other skills, from other repositories
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and inference routing. Covers basic through advanced multi-step workflows. Trigger keywords - openshell, sandbox…
cloud-k8s
Use for authorized cloud, container, and Kubernetes security assessment including metadata SSRF, IAM misconfig, container escape paths, and cluster RBAC review.
kubernetes-specialist
Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies…
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
doca-container-deployment
Use this skill when the user is hands-on deploying an in-bundle DOCA service container (Argus, DMS, Firefly, or UROM service) on a BlueField — kubelet standalone watching a static-pod manifests directory, YAML pod-spec drop, kubelet status / ENTRYPOINT logs / per-service liveness, smoke-before-bulk, and the layered…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.