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-command-manualnpx skills add D-Robotics/moss --skill rdk-command-manualgit 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-command-manual)<a href="https://agentmods.dev/skills/d-robotics/moss/rdk-command-manual"><img src="https://agentmods.dev/badge/skills/d-robotics/moss/rdk-command-manual.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.00328 | $0.03047 |
| Opus 5 | $0.00164 | $0.01523 |
| Sonnet 5 | $0.00066 | $0.00609 |
| Haiku 4.5 | $0.00033 | $0.00305 |
Grade B, and why
rdk-command-manual scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
3. For collecting evidence before filing an issue, recommend `sudo rdkos_info -d` (300 log lines) — it bundles hardware model, CPU/BPU status, memory, OS/kernel/miniboot versions. How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RDK Command Manual (RDK-specific commands + Linux command index)
This is the command-as-anchor lookup. The user already knows the command name (or a fragment) and wants its exact syntax, options, typical use, which boards it applies to, and the official source. If instead they have an error/symptom and don't know which command to run, that is rdk-board-knowledge, not this skill.
Sources: D-Robotics official docs. RDK-specific commands come from
rdk_docdocs/09_Appendix/rdk-command-manual/(X-series, category label9.1 RDK专属命令用法) andrdk_s_doc/rdk_doc docs_s/09_Appendix/rdk-command-manual/(S-series).srpi-configlives in02_System_configuration/02_srpi-config.md. The Linux appendix is09_Appendix/linux-command-manual/(label9.2 Linux命令用法). Every fact below was re-verified against these files onmain.
The one thing that matters most
The same command name can behave differently per board. hrut_boardid on X3 has g/s/G/S/c/C sub-options; on X5 it only prints (-h is the sole flag); on S-series it just emits 0x6A84-style output. hrut_somstatus adds a multi-rail voltage block on S-series that X-series never shows. Never recite a command's behavior without first pinning the board. When unsure, tell the user to run which <cmd> or <cmd> -h on the actual board, then explain from the matching doc.
Board → command-availability cheat-sheet
Confirm the board family first, then read the row. "Same" means the command exists with the same core behavior; differences are called out.
| Command | X3 | X5 | Ultra | S100 / S100P / S600 | sudo? |
|---|---|---|---|---|---|
hrut_somstatus |
yes | yes | yes | yes (+ voltage rails, policy-clustered freq, bpu0: ratio only) |
yes |
hrut_boardid |
g/s/G/S/c/C + 32-bit bitfield |
print-only (-h) |
print-only | prints 0x6A84 encoded |
varies |
hrut_socuid |
yes | yes | yes | yes | doc shows sudo on X3 |
hrut_ps |
yes | yes | yes | yes | no |
rdkos_info |
yes (has [ION Memory Size]) |
yes | yes | yes (no ION line; board id 0x6A84) |
yes |
rdk-miniboot-update |
yes | yes | yes | not in S appendix → use OTA flow | yes |
rdk-backup |
yes | yes | yes | not in S appendix | yes |
srpi-config |
yes | yes | NOT Ultra | S100 documented (VNC still being adapted) | yes |
devmem |
yes | yes | yes | yes (identical) | depends on address |
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 · 99 lines · 328 tokens per session scan B cbeedefdcf4d
rdk-command-manual is a skill published in the GitHub repository D-Robotics/moss (142 stars, last pushed 9d ago), licensed MIT. It adds 328 tokens to every session and 3,047 once invoked, about $0.0016 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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…