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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ruvnet/RuViewnpx agentmods add skills/ruvnet/ruview/ruview-configureWrote 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ruvnet/ruview/ruview-configure"><img src="https://agentmods.dev/badge/skills/ruvnet/ruview/ruview-configure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 92 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
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.1 | $0.00067 | $0.01912 |
| Opus 5.5 | $0.00027 | $0.00765 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago First seen · 100 lines · 67 tokens per session scan A 04c781de13e4
ruview-configure is a skill published in the GitHub repository ruvnet/RuView (99,480 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.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.
conducting-wireless-network-penetration-test
Conducts authorized wireless network penetration tests to assess the security of WiFi infrastructure by testing for weak encryption protocols, captive portal bypasses, evil twin attacks, WPA2/WPA3 handshake capture, rogue access point detection, and client-side attacks. The tester evaluates wireless authentication…
beu1000-evuba
A hardware-specific guide for writing firmware for the BE-U1000, a RISC-V microcontroller, on Baikal Electronics EVU-BA development boards. It documents the chip, board wiring, SDK, build setup, and built-in peripherals.
esp32p4-jc-m3-dev
Firmware development for the Guition JC-ESP32P4-M3-DEV board (JC-ESP32P4-M3 module — ESP32-P4NRW32 with 32 MB in-package PSRAM, 16 MB flash, and an ESP32-C6 radio co-processor on SDIO) — its MIPI-DSI panel and MIPI-CSI camera connectors, IP101 Ethernet, ES8311 codec with speaker amplifier and microphone, microSD on…
esp32p4-jc4880p443
Firmware development for the Guition JC4880P443CIW (JC4880P443, JC4880P443C, often mistyped JC4880P433) — a 4.3" 480x800 IPS touch display board on the JC-ESP32P4-M3 module (ESP32-P4NRW32, 32 MB PSRAM, 16 MB flash, ESP32-C6 Wi-Fi co-processor on SDIO) — its ST7701S MIPI-DSI panel, GT911 touch, backlight, ES8311 codec…
esp32-wroom-36pin
Firmware development for the 36-pin ESP32-WROOM-32 development board — the original DOIT ESP32 DevKit V1 with 18 pins per side, i.e. the 30-pin layout plus the six in-package flash pins (SD0 SD1 SD2 SD3 CMD CLK = GPIO6-11) broken out at the USB end, CH340G or CP2102 bridge, AMS1117 LDO, user LED on GPIO2, GPIO0 not on…