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.4.2npx skills add robium-ai/robium --skill 1.4.2git 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.4.2)<a href="https://agentmods.dev/skills/robium-ai/robium/1.4.2"><img src="https://agentmods.dev/badge/skills/robium-ai/robium/1.4.2.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.00131 | $0.03751 |
| Opus 5 | $0.00066 | $0.01876 |
| Sonnet 5 | $0.00026 | $0.00750 |
| Haiku 4.5 | $0.00013 | $0.00375 |
Grade A, and why
testing 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 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.
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.
This is a copy
95% identical to testing — 21 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
testing
The cross-cutting testing umbrella for robium. Robotics apps fail in layers a
generic test suite misses — a node that never receives a message, a launch
file that starts everything except the one node that mattered, a policy that
looks fine on paper but never reaches the goal in sim. This skill frames the
robotics-specific test pyramid and states the non-negotiable bar: a robium
build is not done until its smoke test passes. It does not re-teach
launch_testing/pytest mechanics for ROS 2 (that's ros2) or the
lerobot-eval CLI (that's lerobot) — it frames both as test-pyramid layers
and routes to them.
When to use this skill
- Setting up tests for any new robium project — this should be planned into the build from the start, not bolted on after the fact.
- The trigger phrases in the description: 'test the robot app', 'how do I test this node', 'smoke test', 'regression test in sim'.
- Before claiming any robotics app or sample works — a claim of "done" without a passing smoke test is not verified, it's a guess.
- Load alongside whatever skill is building the thing under test —
ros2/nav2/gazebofor the navigation vertical,lerobotfor the manipulation vertical — this skill supplies the test framing, not a replacement for either. - Cross-references — go to the sibling skill instead when the question is:
- ROS 2
launch_testing/pytest mechanics themselves (fixtures, process actions, assertions) → theros2skill'slaunch-testing-launched-processusage pattern for the four-part scaffold (generate_test_description, ReadyToTest, an active TestCase, @post_shutdown_test), and the upstream launch_testing README and ROS 2 testing docs (linked in References) for full API depth. This skill frames launch/node testing as a pyramid layer either way. - The
lerobot-evalCLI and its flags →lerobot. This skill frames policy eval as a test-pyramid layer with a pass/fail bar;lerobotowns the eval mechanics. - Setting up the simulator a regression test runs against →
gazeboorisaac-sim(orsimulationif the choice isn't made yet). - Where the test data comes from — worlds, robot models, sample
datasets, fixture folders, goldens →
test-assets. This skill decides what to test and when it passes;test-assetssupplies what it runs against. - General (non-robotics) testing practices — unrelated to this skill; use whatever generic testing guidance already applies to the language/ framework in question.
- The whole-stack decision this feeds into →
architect(plans testing into the brief, doesn't bolt it on later).
- ROS 2
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 · 239 lines · 131 tokens per session scan A c11fce0ac9bf
testing is a skill published in the GitHub repository robium-ai/robium (9 stars, last pushed 7d ago), licensed MIT. It adds 131 tokens to every session and 3,751 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to testing, differing in 21 lines, and is treated as a copy.
Other skills, from other repositories
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
backend/testing-guide
后端测试编写指南，包括单元测试、集成测试和E2E测试的编写方法和最佳实践.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
qa/test-strategy
测试策略和测试金字塔原则，定义单元测试、集成测试、E2E测试的分布和覆盖要求.
Codeception Testing
Expert-level Codeception testing skill for PHP applications. Covers acceptance, functional, and unit testing with the Actor pattern, BDD-style syntax, Page Objects, API testing, and database helpers.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.