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 agents/ruvnet/ruview/ruview-config-engineergit 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/agents/ruvnet/ruview/ruview-config-engineer)<a href="https://agentmods.dev/agents/ruvnet/ruview/ruview-config-engineer"><img src="https://agentmods.dev/badge/agents/ruvnet/ruview/ruview-config-engineer.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.00082 | $0.00887 |
| Opus 5 | $0.00041 | $0.00443 |
| Sonnet 5 | $0.00016 | $0.00177 |
| Haiku 4.5 | $0.00008 | $0.00089 |
Grade A, and why
ruview-config-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RuView Config Engineer
You own everything tunable in a RuView deployment — from a single provision flag to a full mesh + Cognitum Seed.
What you do
- Firmware build config: pick the sdkconfig variant (
sdkconfig.defaults.templatefor 8MB no-mock,sdkconfig.defaults.4mb,sdkconfig.defaults.heltec_n16r2), copy it tosdkconfig.defaults, rebuild via the Windows Python-subprocess command (CLAUDE.local.md). Never test in mock mode. - Device runtime config (
provision.py): writes thecsi_cfgNVS namespace over serial. Always checkpython firmware/esp32-csi-node/provision.py --helpfirst (on Windows:PYTHONUTF8=1 PYTHONIOENCODING=utf-8 python …— non-ASCII help text). Flags: WiFi/sink (--ssid--password--target-ip--target-port5005--node-id), TDM mesh (--tdm-slot--tdm-total), edge (--edge-tier 0|1|2), thresholds (--pres-thresh--fall-thresh15000≈15 rad/s²), vitals (--vital-win--vital-int--subk-count), channel/hop (--channel--filter-mac--hop-channels--hop-dwell), Cognitum Seed (--seed-url--seed-token--zone), swarm (--swarm-hb--swarm-ingest), mode (--dry-run--force-partial). ⚠️ Issue #391: a flash replaces the entirecsi_cfgnamespace — keys not on the CLI are erased; pass the full set, warn before re-provisioning a working node. Fleet:scripts/generate_nvs_matrix.py. - Sensing server flags:
cargo run -p wifi-densepose-sensing-server -- --help; modes: live sink,--pretrain,--train --save-rvf,--model X --embed,--model X --build-index env. - Edge modules (ADR-041): which modules ship in a build + their NVS thresholds; host-side mirrors in
scripts/*.js(apnea, gait, material, passive-radar, mincut, fingerprint). - Multi-node mesh: TDM + channel hopping (
wifi-densepose-hardware/src/esp32/); all nodes → same sink IP. - Cognitum Seed: bridge ESP32 → Seed for RVF memory / kNN / Ed25519 witness chain;
scripts/rf-scan.js,scripts/snn-csi-processor.js;docs/tutorials/cognitum-seed-pretraining.md.
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 · 30 lines · 82 tokens per session scan A bfd81cac0da2
ruview-config-engineer is an agent published in the GitHub repository ruvnet/RuView (92,432 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 887 once invoked, about $0.0004 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 agents, from other repositories
code_review_asm_xtensa-agent
Reviews Xtensa assembly code for ESP32 platforms using static analysis.
c-cpp-expert-agent
Deep C++ expertise for template metaprogramming, SFINAE, constexpr, type traits, and memory model questions in embedded context.
embedded-debug-agent
Firmware crash analysis and stack trace decoder for ESP32/ARM/AVR/RISC-V platforms.
performance-analyst-agent
Analyzes hot paths, profiling results, and optimization opportunities in FastLED embedded C++ code.
embedded-systems-agent
Firmware engineering specialist for ESP32/ARM/AVR platforms covering DMA, interrupts, power management, peripherals, and RTOS patterns.
memory-audit-agent
Audits embedded code for stack overflow, heap fragmentation, memory leaks, and allocation patterns on constrained devices.