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/d-robotics/moss/rdk-source-mapnpx skills add D-Robotics/moss --skill rdk-source-mapgit clone --depth 1 https://github.com/D-Robotics/mossWhat 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.00296 | $0.03347 |
| Opus 5 | $0.00148 | $0.01673 |
| Sonnet 5 | $0.00059 | $0.00669 |
| Haiku 4.5 | $0.00030 | $0.00335 |
Grade A, and why
rdk-source-map 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 3d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
D-Robotics GitHub Org Repo Map
Help a user who is staring at the D-Robotics org (226 public repos, 327 total including private) and cannot tell which repo is which. This skill answers four questions: what is this repo, what layer/board does it belong to, which repo should I use for my task, and how do I build an image/workspace from source. The single most important rule: hobot- (hyphen) and hobot_ (underscore) are two different systems — get that wrong and every downstream answer is wrong.
Sources: live
gh api orgs/D-Robotics/reposmetadata (verified 2026-06, 226 public / 327 total) plus the READMEs of rdk-gen, manifest, and robot_dev_config. Repo counts drift as the org evolves — re-rungh apito confirm before quoting an exact number.
The one distinction that matters most: hyphen vs underscore
Verified by name across all public repos (2026-06): ~20 hobot-* (hyphen) vs ~38 hobot_* (underscore). They are NOT stylistic variants of the same thing. (Counts drift — gh api orgs/D-Robotics/repos --paginate --jq '.[].name' | grep -c '^hobot-' to recount.)
hobot-xxx (hyphen) |
hobot_xxx (underscore) |
|
|---|---|---|
| Layer | BSP / system source (goes into the OS image) | TROS / ROS2 application package |
| Examples | hobot-boot, hobot-camera, hobot-multimedia, hobot-bpu-drivers, hobot-dnn (low-level lib) |
hobot_dnn (dnn_node), hobot_stereonet, hobot_usb_cam, hobot_llamacpp |
| Assembled by | repo + manifest + *-rdk-gen → system image |
vcstool + robot_dev_config/ros2.repos → TROS workspace |
| Language | C / Shell / config | C++ / Python (ROS packages) |
Same name across layers:
hobot-dnn(hyphen — the low-level BPU inference library inside the image) is wrapped byhobot_dnn(underscore — the ROS2dnn_nodepackage). The rule of thumb: upper ROS node (underscore) → lower BSP library (hyphen). When a user says "hobot_dnn vs hobot-dnn," this is the answer.
What ships with it
3 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.
- 3d ago First seen · 116 lines · 296 tokens per session scan A bbe6663393bb
rdk-source-map is a skill published in the GitHub repository D-Robotics/moss (142 stars, last pushed 7d ago), licensed MIT. It adds 296 tokens to every session and 3,347 once invoked, about $0.0015 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-08-30.
Other skills, from other repositories
add-macos-statusbar
Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.
cli-anything-3mf
3MF mesh geometry editor — detect and resize cylindrical holes, repair meshes, compare 3D printing files. Works with BambuStudio and PrusaSlicer 3MF files.
platform-port
Guide porting FastLED to new MCU platforms, including int.h types, clockless drivers, SPI implementations, and platform detection. Use when adding support for a new microcontroller family or board.
doca-compress
Use this skill for hands-on DOCA Compress programming on a BlueField DPU, ConnectX NIC, or host with DOCA — enabling compress-deflate, decompress-deflate, decompress-lz4-stream, or decompress-lz4-block tasks on a docacompress context (the hardware supports DEFLATE both directions plus LZ4 decompress; LZ4 encode is NOT…
pcbway
PCBWay PCB fabrication and assembly — turnkey/consigned assembly, design rules, ordering workflow. Alternative to JLCPCB for manufacturing. Use with KiCad. Use this skill when the user mentions PCBWay, needs turnkey assembly (PCBWay sources parts by MPN), has parts not available on LCSC, needs assembled boards with…
anta-validation
Validate Arista EOS network state with structured pass/fail verdicts using ANTA. Use for "is this switch healthy", "did my change break anything", "verify BGP/interfaces/hardware are correct", "run a health check on this device". Read-only. A test for a feature the device does not run reports notapplicable — never a…