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/gazebonpx skills add robium-ai/robium --skill gazebogit 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/gazebo)<a href="https://agentmods.dev/skills/robium-ai/robium/gazebo"><img src="https://agentmods.dev/badge/skills/robium-ai/robium/gazebo.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.1 | $0.00147 | $0.05342 |
| Opus 5 | $0.00073 | $0.02671 |
| Sonnet 5 | $0.00029 | $0.01068 |
| Haiku 4.5 | $0.00015 | $0.00534 |
Grade B, and why
gazebo scanned grade B with 2 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt-get install ros-jazzy-ros-gz Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
and **Harmonic** (LTS, Sep 2023 – May 2029); verified by direct `curl` of This is a copy
100% identical to gazebo — 103 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gazebo
The sim half of the robium nav-vertical trial run: modern Gazebo (the gz
tools; Gazebo Classic/gazebo11 is a separate, EOL project and out of scope
everywhere in this skill) for building SDF worlds and models, attaching
sensors, bridging topics to ROS 2 via ros_gz, spawning robots, and running
headless. as of 2026-07-10, Gazebo's current named releases are Jetty
(LTS, Sep 2025 – May 2031), Ionic (standard support, Sep 2024 – Dec 2026),
and Harmonic (LTS, Sep 2023 – May 2029); verified by direct curl of
gazebosim.org/docs/all/releases/ on 2026-07-10, which also lists the older
Fortress LTS (Sep 2021 – May 2027) still inside its support window. Jetty is
now the newest LTS, one release past the Harmonic/Ionic line named in this
skill's description; re-verify the release list before trusting any of this
paragraph in a future session; see references/worlds-and-models.md's
sourcing note. The robium nav vertical (nav2 skill) targets ROS 2 Jazzy
Jalisco, whose paired Gazebo release is Harmonic; the ros_gz
jazzy branch ships prebuilt binaries for that pairing from
packages.ros.org, confirmed by direct fetch of the ros_gz README this
session (see References). This skill's nav-facing snippets and examples
target Jazzy + Harmonic for that reason; Ionic (paired with Kilted) is
nearing its Dec 2026 EOL, and Jetty (the newest LTS) pairs with Lyrical or
Rolling, not Jazzy; don't pick either for a new Jazzy-based project without
re-checking the table first.
When to use this skill
- Building or editing an SDF world or model, adding a sensor (lidar, camera,
IMU, contact) to a robot, wiring a
ros_gzbridge, spawning a robot into a running simulation, or running Gazebo headless/server-only. - The trigger phrases in the description: 'gazebo', 'gz sim', 'ros_gz', 'simulate the robot', 'add a lidar to the sim'.
- Someone mentions Gazebo Classic tutorials,
gazebo11, or the oldlibgazebo_ros_*plugin names; flag that they don't apply here (Classic is EOL) and redirect to this skill's moderngz/ros_gzequivalents. - Cross-references: go to the sibling skill instead when the question is:
- Which simulator to use at all (Gazebo vs. Isaac Sim vs. something
else) → the
simulationskill. This skill assumes Gazebo has already been chosen. - Generic ROS 2 mechanics the bridge or a spawned robot's launch file rides
on (workspaces, colcon, launch files, TF2 concepts, QoS) →
ros2. This skill's only TF content is what theros_gzbridge or a sim plugin itself publishes. - Navigation behavior once sensor data is flowing (costmaps, AMCL,
behavior trees) →
nav2. This skill stops at "sensor topics are bridged and correctly framed"; what Nav2 does with them isnav2's territory. - Isaac Sim specifically →
isaac-sim. - Running
gz/ros_gzinside Docker, GPU passthrough for the container, or macOS/remote-server environment strategy →environments. This skill's Platform gotchas section only notes where Docker changes gz's own behavior (rendering, display), not how to set the container up. - The whole-stack decision this feeds into →
architect(routes here).
- Which simulator to use at all (Gazebo vs. Isaac Sim vs. something
else) → the
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.
- 6d ago First seen · 323 lines · 147 tokens per session scan B 9588e6579abc
gazebo is a skill published in the GitHub repository robium-ai/robium (9 stars, last pushed 8d ago), licensed MIT. It adds 147 tokens to every session and 5,342 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). It is 100% identical to gazebo, differing in 103 lines, and is treated as a copy.
Other skills, from other repositories
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-writing-skills
Authoring discipline for new IJFW skills. Use when creating a new skill, writing a skill, making a skill that does X, or asked to add a skill. Trigger: create a new skill, write a skill, new skill, make me a skill, skill that does, /ijfw-writing-skills.