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.
npx agentmods add commands/ruvnet/ruview/auto-topologygit 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/auto-topology)<a href="https://agentmods.dev/commands/ruvnet/ruview/auto-topology"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/auto-topology.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.00000 | $0.00363 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
auto-topology 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 5d 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:
- auto-topology — 100% identical, 0 lines differ
- auto-topology — 100% identical, 0 lines differ
- auto-topology — 100% identical, 0 lines differ
- auto-topology — 100% identical, 0 lines differ
- auto-topology — 100% identical, 13 lines differ
- auto-topology — 100% identical, 0 lines differ
- auto-topology — 100% identical, 0 lines differ
- auto-topology — 100% identical, 0 lines differ
What it actually says
Automatic Topology Selection
Purpose
Automatically select the optimal swarm topology based on task complexity analysis.
How It Works
1. Task Analysis
The system analyzes your task description to determine:
- Complexity level (simple/medium/complex)
- Required agent types
- Estimated duration
- Resource requirements
2. Topology Selection
Based on analysis, it selects:
- Star: For simple, centralized tasks
- Mesh: For medium complexity with flexibility needs
- Hierarchical: For complex tasks requiring structure
- Ring: For sequential processing workflows
3. Example Usage
Simple Task:
Tool: mcp__claude-flow__task_orchestrate
Parameters: {"task": "Fix typo in README.md"}
Result: Automatically uses star topology with single agent
Complex Task:
Tool: mcp__claude-flow__task_orchestrate
Parameters: {"task": "Refactor authentication system with JWT, add tests, update documentation"}
Result: Automatically uses hierarchical topology with architect, coder, and tester agents
Benefits
- 🎯 Optimal performance for each task type
- 🤖 Automatic agent assignment
- ⚡ Reduced setup time
- 📊 Better resource utilization
Hook Configuration
The pre-task hook automatically handles topology selection:
{
"command": "npx claude-flow hook pre-task --optimize-topology"
}
Direct Optimization
Tool: mcp__claude-flow__topology_optimize
Parameters: {"swarmId": "current"}
CLI Usage
# Auto-optimize topology via CLI
npx claude-flow optimize topology
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.
- 5d ago First seen · 62 lines · 0 tokens per session scan A b1eadd2b29da
auto-topology is a command published in the GitHub repository ruvnet/RuView (92,510 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 363 tokens. 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-08-30.
Other commands, from other repositories
fix_board
Automatically diagnose and fix PlatformIO board upload/monitor issues.
test
Run tests using uv run test.py with optional arguments.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
gh-pr
Create (or update) a Pull Request.
release
Release a new version of rubyllm-agents to RubyGems and GitHub.
ccboard-web
Launch ccboard web interface.