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.
git 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/review-diff)<a href="https://agentmods.dev/commands/ruvnet/ruview/review-diff"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/review-diff/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/commands/ruvnet/ruview/review-diff"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/review-diff.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.00077 |
| Opus 5.5 | $0.00005 | $0.00031 |
| Sonnet 5.5 | $0.00003 | $0.00015 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
review-diff 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- review-diff — 100% identical, 0 lines differ
What it actually says
Review the current git diff.
git diffto read the change.- Report only high-confidence findings as
file:line — issue — fix. - Separate bugs from nits.
- End with APPROVE or REQUEST-CHANGES and a one-line reason.
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 · 11 lines · 13 tokens per session scan A 2ab52f01487b
review-diff is a command published in the GitHub repository ruvnet/RuView (98,920 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 77 once invoked, about $0.0001 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 commands, from other repositories
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
gsd:pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
pr-risk
Calculate a composite PR risk score (size, complexity, test coverage, dependencies, security) before merging or reviewing. Detects large PRs needing splits and generates a context-aware pre-merge checklist. Run before /review-pr or before opening a PR. Usage: /pr-risk [branch or commit range] (default: HEAD1..HEAD).
recreate-pr
Create a copy of an existing PR with review comments summarized as fixes. This allows Gemini (or other reviewers) to re-review the changes.