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 skills add ruvnet/RuView --skill pair-programminggit 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/skills/ruvnet/ruview/pair-programming)<a href="https://agentmods.dev/skills/ruvnet/ruview/pair-programming"><img src="https://agentmods.dev/badge/skills/ruvnet/ruview/pair-programming/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/skills/ruvnet/ruview/pair-programming"><img src="https://agentmods.dev/badge/skills/ruvnet/ruview/pair-programming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 872 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00061 | $0.06280 |
| Opus 5.5 | $0.00024 | $0.02512 |
| Sonnet 5.5 | $0.00012 | $0.01256 |
| Haiku 4.5 | $0.00006 | $0.00628 |
Grade A, and why
Pair Programming 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:
- Pair Programming — 100% identical, 0 lines differ
- Pair Programming — 100% identical, 256 lines differ
- Pair Programming — 100% identical, 0 lines differ
- Pair Programming — 100% identical, 0 lines differ
- Pair Programming — 100% identical, 0 lines differ
- Pair Programming — 100% identical, 256 lines differ
- Pair Programming — 100% identical, 124 lines differ
- Pair Programming — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pair Programming
Collaborative AI pair programming with intelligent role management, real-time quality monitoring, and comprehensive development workflows.
What This Skill Does
This skill provides professional pair programming capabilities with AI assistance, supporting multiple collaboration modes, continuous verification, and integrated testing. It manages driver/navigator roles, performs real-time code review, tracks quality metrics, and ensures high standards through truth-score verification.
Key Capabilities:
- Multiple Modes: Driver, Navigator, Switch, TDD, Review, Mentor, Debug
- Real-Time Verification: Automatic quality scoring with rollback on failures
- Role Management: Seamless switching between driver/navigator roles
- Testing Integration: Auto-generate tests, track coverage, continuous testing
- Code Review: Security scanning, performance analysis, best practice enforcement
- Session Persistence: Auto-save, recovery, export, and sharing
Prerequisites
Required:
- Claude Flow CLI installed (
npm install -g claude-flow@alpha) - Git repository (optional but recommended)
Recommended:
- Testing framework (Jest, pytest, etc.)
- Linter configured (ESLint, pylint, etc.)
- Code formatter (Prettier, Black, etc.)
Quick Start
Basic Session
# Start simple pair programming
claude-flow pair --start
TDD Session
# Test-driven development
claude-flow pair --start \
--mode tdd \
--test-first \
--coverage 90
Complete Guide
Session Control Commands
Starting Sessions
# Basic start
claude-flow pair --start
# Expert refactoring session
claude-flow pair --start \
--agent senior-dev \
--focus refactor \
--verify \
--threshold 0.98
# Debugging session
claude-flow pair --start \
--agent debugger-expert \
--focus debug \
--review
# Learning session
claude-flow pair --start \
--mode mentor \
--pace slow \
--examples
Session Management
# Check status
claude-flow pair --status
# View history
claude-flow pair --history
# Pause session
/pause [--reason <reason>]
# Resume session
/resume
# End session
claude-flow pair --end [--save] [--report]
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 · 1,203 lines · 61 tokens per session scan A 32ef344d86f6
Pair Programming is a skill published in the GitHub repository ruvnet/RuView (98,528 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 6,280 once invoked, about $0.0002 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 skills, from other repositories
user-story-writer
Escribir historias de usuario bien estructuradas con criterios de aceptación y casos extremos. Úsalo cuando te pidan escribir historias de usuario, crear tickets a partir de un resumen de características, convertir un PRD en historias o redactar criterios de aceptación. Produce historias listas para estimar en formato…
testing-principles
Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof ownership, with frontend and browser E2E implementation references. Use when writing tests, deciding test scope, or reviewing test quality.
test-driven-development
Enforces TDD discipline with RED-GREEN-REFACTOR cycle. Use when writing new features, fixing bugs, or refactoring code. Ensures tests genuinely verify behavior.
pair-programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
add
Use this skill when the user wants AI work they can trust without watching every step: the AI fixes direction first (rules, assumptions, failing checks sealed in git), builds to green, then proves the result with evidence for the human to review. Trigger when a repo has .add/, the user says "add", "/add", "start a…
run-feedback
Use when a run of a workflow, skill, command, or test produced errors or friction worth keeping, or when executing the end-of-run Retro Global Protocol — collect findings into the feedback inbox, triage them (defect / work-item / noise), and file defects into the known-issues ledger or work-items into the backlog. NOT…