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-verifygit 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/commands/ruvnet/ruview/ruview-verify)<a href="https://agentmods.dev/commands/ruvnet/ruview/ruview-verify"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/ruview-verify.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.00033 | $0.00340 |
| Opus 5 | $0.00016 | $0.00170 |
| Sonnet 5 | $0.00007 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
ruview-verify 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-verify
Run RuView's trust pipeline.
- Invoke the
ruview-verifyskill. - Based on
$ARGUMENTS(defaultall):- tests —
cd v2 && cargo test --workspace --no-default-features(1,400+ pass, 0 fail). - proof —
python archive/v1/data/proof/verify.py(must printVERDICT: PASS; if hash drift from a legit numpy/scipy bump,--generate-hashthen re-run). Optionallycd archive/v1 && python -m pytest tests/ -x -q. - bundle —
bash scripts/generate-witness-bundle.sh, thencd dist/witness-bundle-ADR028-*/ && bash VERIFY.sh(must be 7/7 PASS). - all — do all of the above in order.
- tests —
- If this follows a code change, walk the pre-merge checklist from
CLAUDE.md(README/CLAUDE.md/CHANGELOG/user-guide updates, ADR count, witness bundle regen, Docker rebuild only if needed, crate publishing in dependency order,.gitignore, security review for hardware/network modules). - For security-related changes also run
npx @claude-flow/cli@latest security scan.
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 · 18 lines · 33 tokens per session scan A 679c975ec178
ruview-verify is a command published in the GitHub repository ruvnet/RuView (92,432 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 340 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 commands, from other repositories
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.
rvcsi-nexmon
Nexmon CSI helpers — inspect a nexmoncsi .pcap, decode a Broadcom chanspec, or list the known Nexmon chips / Raspberry-Pi models.
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…
review-firmware
Run embedded firmware code review (memory safety, ISR, RTOS, C/C++ UB).
monitor
Command "monitor" from chayuto/ws-ESP32-S3-CAM, covering read serial output from the board, fix 1 — stty -hupcl + dd (works reliably), fix 2 — pyserial but set dtr/rts before open, optional: pulse rts only to reset without touching dtr and healthy read (once the dtr trap is avoided).
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.