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-hardwarenpx skills add D-Robotics/moss --skill rdk-hardwaregit clone --depth 1 https://github.com/D-Robotics/mossWrote 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/d-robotics/moss/rdk-hardware)<a href="https://agentmods.dev/skills/d-robotics/moss/rdk-hardware"><img src="https://agentmods.dev/badge/skills/d-robotics/moss/rdk-hardware.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.00332 | $0.03302 |
| Opus 5 | $0.00166 | $0.01651 |
| Sonnet 5 | $0.00066 | $0.00660 |
| Haiku 4.5 | $0.00033 | $0.00330 |
Grade A, and why
rdk-hardware 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RDK Hardware & System Facts
The single most important rule: per-board hardware facts are NOT uniform — confirm the board first, then read its row. Pin voltage, power-LED color, default IP, CAN type, and model format all differ across the six boards. Reciting a "typical RDK board" from memory is how wrong answers happen.
Sources: official D-Robotics hardware-introduction docs —
rdk_x_doc(X3/X5),rdk_doc(Ultra),rdk_s_doc(S100/S600). Re-verified against those pages. Per-board numbers are pinned in board-specs.md; deterministic lookup inscripts/board_specs.py.
Confirm the board first
cat /sys/class/socinfo/board_id # universal, all boards
cat /proc/device-tree/model # board name string
cat /etc/version # OS image version (rdkos_info on 2.1.0+)
Never assume the board. An X3 pinout handed to an X5 user, or a SocketCAN command on an S100, is a real and common failure.
The 6-board hardware cheat-sheet
| Board | BPU arch | INT8 TOPS | RAM | Model | OS / TROS | Power & LED | 40PIN IO | CAN | Default eth IP |
|---|---|---|---|---|---|---|---|---|---|
| X3 | Bernoulli2 | 5 | 2 GB | .bin |
22.04 / Humble | 5V/3A USB-C, red LED | 3.3V | none | 192.168.1.10 (.127.10 on 2.1.0+) |
| X5 | Bayes-e | 10 | 4/8 GB | .bin |
22.04 / Humble | 5V/5A USB-C, green+orange | 3.3V | SocketCAN can0 (TCAN4550) |
192.168.127.10 |
| Ultra | Bayes | 96 | 8 GB | .bin |
22.04 / Humble | ≥12V/5A DC, red LED | 3.3V | none | 192.168.1.10 |
| S100 | Nash-e | 80 | 12 GB | .hbm |
22.04 / Humble | 12–20V DC, green+orange | 3.3V | MCU CANHAL (CAN5–9) | eth1 fixed 192.168.127.10 |
| S100P | Nash-m | 128 | 24 GB | .hbm |
22.04 / Humble | 12–20V DC, green+orange | 3.3V | MCU CANHAL (CAN5–9) | eth1 fixed 192.168.127.10 |
| S600 | Nash | 560 | 32/64 GB | .hbm |
24.04 / Jazzy | 12–28V DC, green+orange | 1.8V, NO 40PIN | MCU CANHAL (MCU×5 + Main×4) | eth1 fixed 192.168.127.10 |
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.
- 5d ago First seen · 107 lines · 0 tokens per session scan A c3919dbdc8d3
rdk-hardware is a skill published in the GitHub repository D-Robotics/moss (142 stars, last pushed 9d ago), licensed MIT. It adds 332 tokens to every session and 3,302 once invoked, about $0.0017 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
integrated-browser
Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under src/vs/platform/browserView and src/vs/workbench/contrib/browserView.
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…