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 commands/ruvnet/ruview/ruview-startgit 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.00027 | $0.00328 |
| Opus 5 | $0.00014 | $0.00164 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
ruview-start 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
/ruview-start
Onboard the user onto RuView (WiFi-DensePose).
- Invoke the
ruview-quickstartskill. - If
$ARGUMENTSnames a tier (docker,build,hardware), go straight to it; otherwise ask which hardware they have:- No hardware → Tier 0:
docker run -p 3000:3000 ruvnet/wifi-densepose:latest, openhttp://localhost:3000. - Want to build from source → Tier 1:
cd v2 && cargo test --workspace --no-default-features, thenpython archive/v1/data/proof/verify.py. - Have an ESP32-S3 / C6 → Tier 2: hand off to
/ruview-flashthen/ruview-provision, thencargo run -p wifi-densepose-sensing-server.
- No hardware → Tier 0:
- Warn about the gotchas: ESP32-C3 / original ESP32 unsupported; single node = limited spatial resolution; camera-free pose is modest (use camera-supervised for 92.9% PCK@20).
- Point to next steps:
/ruview-app,/ruview-train,/ruview-advanced,/ruview-verify, and theruview-configureskill.
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 · 17 lines · 27 tokens per session scan A d7508c8641f3
ruview-start is a command published in the GitHub repository ruvnet/RuView (92,406 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 328 once invoked, about $0.0001 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 commands, from other repositories
add-ha-entity
Step-by-step guide to add a new Home Assistant entity with MQTT auto-discovery.
flash-size
Analyze firmware binary size and partition layout in detail.
expert_rmt5
ESP-IDF v5.x RMT5 API expert for LED protocols, encoders, and multi-channel control.
aurora
Aurora - independent community smart home orchestrator. Routes any smart home request to the right specialist skill and recommends the correct Claude model. Use this as your starting point for Home Assistant, ESPHome, Node-RED, or any IoT automation task.
hardware-specs
Read this before writing any code that touches peripherals, memory, Wi-Fi, camera, or audio. All GPIO and address numbers below are verified against the vendor BSP (ref/demo/ESP32-S3-CAM-OVxxxx/examples/ESP-IDF-v5.5.1/04dvpcameradisplay/components/waveshareesp32s3camovxxxx/include/bsp/esp32s3camovxxxx.h) and this…
peripherals
Use the vendor BSP waveshare/esp32s3camovxxxx for anything nontrivial. It hides the CH32V003 IO-expander quirks, I²C bus init, camera pin config, and codec addresses. Header: ref/demo/ESP32-S3-CAM-OVxxxx/examples/ESP-IDF-v5.5.1/04dvpcameradisplay/components/waveshareesp32s3camovxxxx/include/bsp/esp32s3camovxxxx.h.