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/ruvnet/ruview/onboardnpx skills add ruvnet/RuView --skill onboardgit clone --depth 1 https://github.com/ruvnet/RuViewWhat 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.00039 | $0.00363 |
| Opus 5 | $0.00019 | $0.00181 |
| Sonnet 5 | $0.00008 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
onboard 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 today.
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.
What it actually says
onboard
Get a newcomer from nothing to a working RuView setup. First fact to set: WiFi
sensing infers coarse pose/presence/breathing from Channel State Information — it
is not a camera, and any accuracy number must be MEASURED against a baseline
(use the verify skill / ruview_claim_check tool). Never present WiFi output as
camera-grade.
Pick a path
Run ruview_onboard {path} or decide from:
- docker-demo — fastest, no hardware. Replays sample CSI into the dashboard.
docker run -p 8000:8000 ruvnet/wifi-densepose→ openhttp://localhost:8000. Use to see what it looks like. - repo-build — for developers.
cd v2 && cargo test --workspace --no-default-features(1,031+ tests pass), thencargo run -p wifi-densepose-cli -- --help. - live-esp32 — a real install. Flash a node (
provision-nodeskill), point it at the sensing-server, thencalibrate-room. This is the only path that senses a real room.
Then
- Live sensing → go to provision-node, then calibrate-room.
- Evaluating a model/claim → go to verify and run
ruview_claim_checkon any report before you quote a number.
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.
- today First seen · 31 lines · 39 tokens per session scan A 97ee71f0aa98
onboard is a skill published in the GitHub repository ruvnet/RuView (92,406 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 363 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
ble
Operate ESP-Claw BLE: initialize BLE, advertise, handle connections, process events, and inspect module state.
nucleo-release
Build, gate, and ship NucleoOS to the Cardputer — firmware via OTA and the web/SD payload via the device file API. Use when the user asks to release, deploy, flash, OTA, sync the SD, or push a web app to the device. Covers the one-command release, firmware-only and SD-only paths, and the gotchas (PIN, .gz shadowing…
nucleo-native-app
Scaffold and implement a NucleoOS native firmware app (C++) correctly — anti-flicker, poll handler, RAM discipline, input routing, registration. Use when creating or fixing a native app in firmware/components/nucleoapp/.
nucleo-release-dual
Build and ship NucleoOS to BOTH Cardputer units — the original and the ADV — in one pass. Use when the user wants to release/build/OTA/flash for both boards, the ADV and non-ADV Cardputers, or two devices at once. Encodes the key fact that it's ONE universal binary (runtime board auto-detect), so you build once and…
cap_router_mgr
Manage router automation rules: list/get/add/update/delete/reload with strict rulejson format.
light_switch
Turn a board light on or off, set LED strip color or brightness, and control GPIO lights. Requires boardhardwareinfo skill.