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 Leehyunbin0131/claude-ros2-skills --skill ros2-developmentgit clone --depth 1 https://github.com/Leehyunbin0131/claude-ros2-skillsWrote 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/leehyunbin0131/claude-ros2-skills/ros2-development)<a href="https://agentmods.dev/skills/leehyunbin0131/claude-ros2-skills/ros2-development"><img src="https://agentmods.dev/badge/skills/leehyunbin0131/claude-ros2-skills/ros2-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/leehyunbin0131/claude-ros2-skills/ros2-development"><img src="https://agentmods.dev/badge/skills/leehyunbin0131/claude-ros2-skills/ros2-development.svg" alt="Reviewed on agentmods" width="80" 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.00067 | $0.01283 |
| Opus 5.5 | $0.00027 | $0.00513 |
| Sonnet 5.5 | $0.00013 | $0.00257 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
ros2-development 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 20d 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROS 2 development
Work from the workspace's actual package graph and installed artifacts. This skill supplies a development workflow, a check for empty test runs, and an optional evidence tracking tool for task handoff. It does not prescribe a new workspace layout or replace the project's build conventions.
Build the affected package graph
Use colcon list to identify package names and build types. Build the changed
package and its workspace dependencies with colcon build --packages-up-to <package>. --packages-select alone does not build its dependencies. For a
message or public API change, include affected consumers in the build and tests.
Preserve the project's existing build/install flags and dependency versions.
Build in a shell with the intended underlay, not the workspace's old overlay.
Use a separate shell to source the resulting install/setup.bash and inspect
ros2 pkg prefix <package>: otherwise an older installed copy can appear to
validate the source change.
Require tests to have run
colcon test and colcon test-result can both succeed with zero tests. Use a
fresh result directory so a previous passing report cannot satisfy this run:
The variable ROS2_SKILL_DIR in the examples below represents the absolute path
to the loaded skill directory. The agent sets this path internally based on
where the skill was discovered and loaded; do not ask the user for this path.
# After building, in the workspace root. Replace my_package with actual names.
# For pytest packages; omit --python-testing pytest for other test frameworks.
ROS2_SKILL_DIR="/absolute/path/to/ros2-development" # Set by agent to loaded skill directory.
results="$(mktemp -d /tmp/ros2-test-results.XXXXXX)"
colcon test --packages-select my_package --return-code-on-test-failure \
--python-testing pytest --test-result-base "$results" &&
python3 "${ROS2_SKILL_DIR}/scripts/check_test_results.py" "$results" \
--packages my_package --require-test my_package::test_changed_behavior
What ships with it
4 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.
- 20d ago Changed · +12 lines b3b374bca89a
- 21d ago Changed · +23 lines 745a6f75f94a
- 22d ago First seen · 69 lines · 67 tokens per session scan A 1404b661016e
ros2-development is a skill published in the GitHub repository Leehyunbin0131/claude-ros2-skills (20 stars, last pushed 20d ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,283 once invoked, about $0.0003 per session on Opus 5.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-25.
Other skills, from other repositories
test-audit
Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fail.
mock-detection
Deep mock appropriateness analysis for Test Audit pipeline.
bug-magnet-data
Curated edge case test data for boundary testing, verification scripts, and test generation. Provides pre-curated reference data organized by data type with context-specific loading guidance.
assertion-patterns
Real output verification vs mock calls. Use when transforming T1-T4 violating tests to verify observable behavior.
test-classification
Prompt template for test classification stage in Test Audit pipeline.
fix-bug
Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.