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/1.3.3npx skills add robium-ai/robium --skill 1.3.3git clone --depth 1 https://github.com/robium-ai/robiumWrote 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/robium-ai/robium/1.3.3)<a href="https://agentmods.dev/skills/robium-ai/robium/1.3.3"><img src="https://agentmods.dev/badge/skills/robium-ai/robium/1.3.3.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.00182 | $0.04814 |
| Opus 5 | $0.00091 | $0.02407 |
| Sonnet 5 | $0.00036 | $0.00963 |
| Haiku 4.5 | $0.00018 | $0.00481 |
Grade A, and why
live-demo 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 5d 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.
- **WebSocket probes need `curl --http1.1`** <!-- id: websocket-probes-need-http1-subprotocol --> against https Cloud Run How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
live-demo
Everything between "the app's smoke test is green" and "a stranger on the website is driving the robot." This skill owns the demo architecture that robium.ai/demos/nav-trial runs in production: a control page whose Start/Stop buttons manage private, per-visitor simulator instances on Cloud Run, a session gateway inside the app container, and a viewer handoff. Every command, flag, and gotcha here was verified live (2026-07-13, nav-trial demo); this is a distillation of a real deployment, not a design sketch.
When to use this skill
- Publishing any robium app as an interactive web demo, and every design choice inside that: flow shape, page anatomy, instance lifecycle, visualizer, budget, and the Cloud Run deployment.
- Debugging a deployed demo (instance won't boot, viewer can't connect, status endpoint misroutes).
- Cross-references: go to the sibling skill instead when the question is:
- The Cloud Run deploy mechanics themselves, meaning the build → Artifact Registry
→
gcloud run deploypath, the sim flag set, billing modes, the gz/DDS transport env vars, session affinity, VPC subnet sizing, deploy auth →cloud-run(this skill owns the orchestrator, gateway, and page; the deploy target under them iscloud-run's). - foxglove_bridge setup, layouts, or MCAP for development use →
foxglove(this skill consumes its bridge; the demo-specific parts (session gateway, deep-link handoff) live here). - Container/compose patterns for the app itself →
integration. - Whether the app is done enough to demo →
testing(smoke test green is this skill's entry bar). - Env reproducibility of the app →
environments.
- The Cloud Run deploy mechanics themselves, meaning the build → Artifact Registry
→
Key directives
- Delegation posture: embed. The demo architecture (gateway contract,
Cloud Run tuning for sims, viewer decision table) exists nowhere
upstream in one place; it was derived by deployment. Bridge mechanics
are
foxglove's; everything demo-shaped is embedded here. - A demo is a product surface: the smoke test extends to it. The app's
demo scenario gets its own gated smoke (
make demo-smoke): WebSocket handshake through the gateway,/startclaim,/statusreachesready, intruder session rejected (409/403), one scripted goal succeeds,/shutdownkills the container. Ship no demo without it. - Scale-to-zero is non-negotiable; per-session cost is explicit.
min-instances=0always. State the per-session cost implication of the billing mode you pick (seereferences/cloud-run-tuning.md); never let an "idle" demo bill silently. - One visitor, one instance, enforced in the gateway. The session UUID claims an instance; a live tunnel is never shareable; an idle claim is takeable (reload semantics). Never rely on Cloud Run routing alone for isolation.
- Lifecycle belongs to something that outlives the instance. The
in-container gateway cannot start or restart itself (it dies with the
container), and a browser cannot start a container, so a real Start
button needs a host-level orchestrator. On Cloud Run the control
plane is that orchestrator, which is why this only becomes visible the
day you run the demo locally. Build it behind a
Driverinterface (LocalDocker now, CloudRun later) rather than special-casing localhost, keep it out of the data path (it hands the browser a per-instance host and gets out of the way), and give it the fleet cap. Seereferences/orchestrator-pattern.md. - Be honest on the page. Cold-boot time (30–90 s, with self-restart on unlucky boots), session caps, and busy states are stated in the demo page's terminal; a demo that pretends to be instant reads as broken the moment it isn't.
What ships with it
5 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.
- 5d ago First seen · 294 lines · 182 tokens per session scan A 4579fd01f1ae
live-demo is a skill published in the GitHub repository robium-ai/robium (9 stars, last pushed 7d ago), licensed MIT. It adds 182 tokens to every session and 4,814 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
terraform-module-library
Build reusable Terraform modules for AWS, Azure, GCP, and OCI infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
ultralytics-platform
This skill should be used when user asks to "upload my model to Ultralytics Platform", "push this run to the platform", "upload a dataset to platform", "download a dataset from platform", "search platform datasets", "start cloud training", "train on platform GPUs", "export a model on platform", "deploy a model…
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".