RuView is a WiFi sensing platform that uses disturbances in radio signals, captured by low-cost ESP32 sensors, to detect presence, movement, breathing, and heart rate without cameras or wearables. It is intended for spatial monitoring and smart-home integrations. The catalogue add-ons support workflows for operating and integrating RuView.
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/ruview-configurenpx skills add ruvnet/RuView --skill ruview-configuregit clone --depth 1 https://github.com/ruvnet/RuViewWrote 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/ruvnet/ruview/ruview-configure)<a href="https://agentmods.dev/skills/ruvnet/ruview/ruview-configure"><img src="https://agentmods.dev/badge/skills/ruvnet/ruview/ruview-configure.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.00067 | $0.01912 |
| Opus 5 | $0.00034 | $0.00956 |
| Sonnet 5 | $0.00013 | $0.00382 |
| Haiku 4.5 | $0.00007 | $0.00191 |
Grade A, and why
ruview-configure 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 yesterday.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RuView Configuration
Everything you can tune in a RuView deployment, from a one-line provision flag to a full mesh + Cognitum Seed setup.
1. Firmware build-time config (sdkconfig)
| Variant | File | When |
|---|---|---|
| 8MB (default) | firmware/esp32-csi-node/sdkconfig.defaults.template |
ESP32-S3 8MB, full feature set, real WiFi CSI |
| 4MB | firmware/esp32-csi-node/sdkconfig.defaults.4mb |
ESP32-S3 SuperMini 4MB — display disabled, dual OTA slots (partitions_4mb.csv, ~1.856 MB each) |
| Heltec N16R2 | firmware/esp32-csi-node/sdkconfig.defaults.heltec_n16r2 |
Heltec boards |
Switch: cp firmware/esp32-csi-node/sdkconfig.defaults.<variant> firmware/esp32-csi-node/sdkconfig.defaults, then rebuild (see ruview-hardware-setup). Never test in mock mode — the Kconfig fall-threshold bug only showed up with real CSI.
2. Runtime device config (NVS via provision.py)
provision.py writes the csi_cfg NVS namespace over the serial port. Run python firmware/esp32-csi-node/provision.py --help for the authoritative flag list (on Windows force PYTHONUTF8=1 PYTHONIOENCODING=utf-8 — the help text contains non-ASCII and crashes under cp1252).
python firmware/esp32-csi-node/provision.py --port COM8 \
--ssid "WiFi" --password "secret" \
--target-ip 192.168.1.20 --target-port 5005 \ # aggregator UDP sink (port default 5005)
--node-id 1 \ # 0-255
--channel 6 --filter-mac AA:BB:CC:DD:EE:FF # ADR-060: pin channel + filter transmitter
| Flag group | Flags | Notes |
|---|---|---|
| WiFi / sink | --ssid --password --target-ip --target-port (5005) --node-id |
--node-id 0-255 |
| TDM mesh | --tdm-slot --tdm-total |
0-based slot index + total node count — this is how multi-node mesh is slotted |
| Edge processing | --edge-tier {0,1,2} |
0=off, 1=stats, 2=vitals (ADR-041) |
| Detection thresholds | --pres-thresh (50) --fall-thresh (15000 → 15.0 rad/s²) |
raise --fall-thresh to cut false falls in high-traffic areas (issue #263) |
| Vitals | --vital-win (300 frames) --vital-int (1000 ms) --subk-count (32, top-K subcarriers) |
|
| Channel / hopping | --channel (1-14 / 36-177, overrides AP auto-detect) --filter-mac --hop-channels (1,6,11) --hop-dwell (200 ms) |
omit --channel + set --hop-channels for ADR-061 multi-freq hopping; omit --filter-mac to capture all transmitters |
| Cognitum Seed | --seed-url (http://10.1.10.236) --seed-token (Bearer, from pairing) --zone (lobby) |
|
| Swarm | --swarm-hb (30 s) --swarm-ingest (5 s) |
heartbeat + vector ingest intervals |
| Mode | --dry-run (build NVS bin, don't flash) --baud (460800) --force-partial |
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.
- yesterday First seen · 100 lines · 67 tokens per session scan A 04c781de13e4
ruview-configure is a skill published in the GitHub repository ruvnet/RuView (92,510 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 1,912 once invoked, about $0.0003 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
meraki-wireless-ops
Cisco Meraki wireless (read-only) — SSID configuration, RF profiles, Air Marshal, channel utilization, signal quality, client connectivity events via Cisco's official Meraki MCP. Use when inspecting Meraki SSIDs, auditing RF configuration, or investigating WiFi connectivity.
driver-review
Review and implement hardware driver code — DMA safety, interrupt correctness, timing constraints, peripheral register usage, channel drivers, and peripheral mock implementations. Use when writing, modifying, or reviewing LED drivers, SPI/I2S/RMT/UART/PARLIO/LCDCAM peripherals, GPIO configuration, or peripheral mock…
esp32-arch-review
Review ESP32 FastLED firmware architecture for RTOS safety, DMA correctness, LED driver patterns, memory management, and peripheral safety. Use before merging significant driver changes, new platform ports, or when auditing existing ESP32 FastLED code.
esp32-log-triage
Parse and classify ESP32 serial log output to identify FastLED-related errors, RMT/I2S/SPI driver faults, timing violations, RTOS issues, and crash signatures. Use when debugging unexpected device behavior, boot failures, or LED output problems on ESP32.
embedded-debug
Firmware crash analysis, stack trace decoder, and register dump interpreter for ESP32/ARM/AVR platforms. Use when debugging device crashes, panics, guru meditation errors, hard faults, or analyzing core dumps.
memory-audit
Audit embedded code for stack overflow risks, heap fragmentation, static allocation patterns, and memory leaks. Use when investigating OOM crashes, optimizing memory usage, or reviewing memory-critical code on constrained devices.