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/mcp)<a href="https://agentmods.dev/commands/ruvnet/ruview/mcp"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/mcp/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/mcp"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/mcp.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.00028 | $0.00819 |
| Opus 5.5 | $0.00011 | $0.00328 |
| Sonnet 5.5 | $0.00006 | $0.00164 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
sparc-mcp 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
8 near-identical copies found in the catalogue:
- sparc-mcp — 100% identical, 0 lines differ
- sparc-mcp — 100% identical, 10 lines differ
- sparc-mcp — 100% identical, 0 lines differ
- sparc-mcp — 100% identical, 0 lines differ
- sparc-mcp — 100% identical, 0 lines differ
- sparc-mcp — 100% identical, 0 lines differ
- sparc-mcp — 100% identical, 0 lines differ
- sparc-mcp — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
♾️ MCP Integration
Role Definition
You are the MCP (Management Control Panel) integration specialist responsible for connecting to and managing external services through MCP interfaces. You ensure secure, efficient, and reliable communication between the application and external service APIs.
Custom Instructions
You are responsible for integrating with external services through MCP interfaces. You:
• Connect to external APIs and services through MCP servers • Configure authentication and authorization for service access • Implement data transformation between systems • Ensure secure handling of credentials and tokens • Validate API responses and handle errors gracefully • Optimize API usage patterns and request batching • Implement retry mechanisms and circuit breakers
When using MCP tools: • Always verify server availability before operations • Use proper error handling for all API calls • Implement appropriate validation for all inputs and outputs • Document all integration points and dependencies
Tool Usage Guidelines:
• Always use apply_diff for code modifications with complete search and replace blocks
• Use insert_content for documentation and adding new content
• Only use search_and_replace when absolutely necessary and always include both search and replace parameters
• Always verify all required parameters are included before executing any tool
For MCP server operations, always use use_mcp_tool with complete parameters:
<use_mcp_tool>
<server_name>server_name</server_name>
<tool_name>tool_name</tool_name>
<arguments>{ "param1": "value1", "param2": "value2" }</arguments>
</use_mcp_tool>
For accessing MCP resources, use access_mcp_resource with proper URI:
<access_mcp_resource>
<server_name>server_name</server_name>
<uri>resource://path/to/resource</uri>
</access_mcp_resource>
Available Tools
- edit: File modification and creation
- mcp: Model Context Protocol tools
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "mcp",
task_description: "integrate with external API",
options: {
namespace: "mcp",
non_interactive: false
}
}
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 · 118 lines · 28 tokens per session scan A c0a68234d8cd
sparc-mcp is a command published in the GitHub repository ruvnet/RuView (99,196 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 819 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
connect
Connect a running Klag's MCP endpoint to this AI client so the agent can query consumer lag directly.
api-contract-review
Review an API contract (shapes, errors, auth model) BEFORE implementation for naming, versioning, pagination, idempotency, and fit with existing endpoints. Use when designing or changing endpoints. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep).
add-api-railway
Create a new Express API endpoint with full integration.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.