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 skills add robium-ai/robium --skill rviz2git 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/rviz2)<a href="https://agentmods.dev/skills/robium-ai/robium/rviz2"><img src="https://agentmods.dev/badge/skills/robium-ai/robium/rviz2.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 60 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00018 | $0.00481 |
| Opus 5 | $0.00009 | $0.00241 |
| Sonnet 5 | $0.00004 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
rviz2 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 today.
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
RViz2
Treat RViz2 as a consumer of ROS evidence. A blank display usually means its frame, message, QoS, or time contract is wrong.
Build a focused view
- Start with a fixed frame that exists now, then add only the displays needed for the question being asked.
- Prefer adding by topic when discovering a graph; it helps match message type to display type.
- Keep a saved
.rvizconfiguration per robot and task. Do not rebuild the display list on every run or make one unreadable everything-dashboard. - For navigation, view raw sensors and TF alongside map, costmaps, footprint, plan, and robot model so upstream data can be distinguished from Nav2 output.
Read what the display is telling you
- A red or empty display is evidence about the input boundary, not proof that RViz itself is broken.
- Check fixed frame and TF first, then publisher/display QoS, then simulation
time and
/clock. - Compare the configured topic and namespace with the live graph; stale configs often point at an old robot name.
- A missing display plugin can fail one saved display while the rest of the config continues to load.
Read failures when something does not render. Cross into ros2
only when the evidence points to TF, QoS, graph, or time at the publisher. Cross
into navigation when those inputs are healthy but a costmap, plan, or
controller result is wrong.
Use foxglove instead for a headless, remote, browser, or shareable workflow;
use rerun for data-centric ML and non-ROS logging. If the viewer has not been
chosen, use visualization first.
Done
- The fixed frame is present and every displayed message transforms into it.
- Display QoS and topic namespaces match their publishers.
- Simulation time is consistent when applicable.
- The saved config opens into a focused, useful debugging view.
- Any CLI or UI details were checked against the installed RViz2 build and current RViz documentation.
What ships with it
1 file 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.
- today Changed · -164 lines · -88 tokens per session 791f6168d742
- 4d ago First seen · 214 lines · 106 tokens per session scan A d1a4f486b7ae
rviz2 is a skill published in the GitHub repository robium-ai/robium (9 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 481 once invoked, about $0.0001 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
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when a device is unreachable, a user reports connectivity problems, an interface…
ipfabric
Skill: /ipfabric MCP Server: ipfabric-mcp (remote HTTP via mcp-remote) Tools: 10 (health, path lookups, diagrams, API discovery).