rvcsi-inspect

rvcsi-inspect is a command for Claude Code from ruvnet/rvcsi. It costs 28 tokens per session (299 once invoked), scanned A, original, Apache-2.0.

A command that summarizes a .rvcsi wireless capture, a file containing recorded Wi-Fi channel-state measurements.

In plain words
What is it for?
Use it to review capture duration, frame counts, channels, subcarriers, quality, validation results, and calibration information before running analysis.
Why use it?
It quickly shows whether the recording is complete and consistent, and flags rejected frames, mixed formats, failed channel detection, or low signal quality.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the rvcsi plugin — 5 commands, 1 agent shipped together

Good fit Use it to review capture duration, frame counts, channels, subcarriers, quality, validation results, and calibration information before running analysis.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ruvnet/rvcsi/rvcsi-inspect
View source ↗ ruvnet/rvcsi
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ruvnet/rvcsi

Made for: Claude Code.

Or install rvcsi, the plugin that ships this one along with the rest of its 5 commands, 1 agent.

Wrote 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.

agentmods badge for rvcsi-inspect

README.md
[![agentmods](https://agentmods.dev/badge/commands/ruvnet/rvcsi/rvcsi-inspect.svg)](https://agentmods.dev/commands/ruvnet/rvcsi/rvcsi-inspect)
Your own site
<a href="https://agentmods.dev/commands/ruvnet/rvcsi/rvcsi-inspect"><img src="https://agentmods.dev/badge/commands/ruvnet/rvcsi/rvcsi-inspect.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 299 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00299
Opus 5 $0.00014 $0.00150
Sonnet 5 $0.00006 $0.00060
Haiku 4.5 $0.00003 $0.00030

Measured 8d ago against content hash 6d967cfe47bd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

rvcsi-inspect 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 8d 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.

plugins/rvcsi/commands/rvcsi-inspect.md · 14 lines

What it actually says

/rvcsi-inspect

Print a one-screen summary of a .rvcsi capture.

  1. Run rvcsi inspect <file.rvcsi> (add --json for machine-readable output) — or cargo run -p rvcsi-cli -- inspect <file.rvcsi> in a checkout.
  2. Report: capture version, session/source ids, adapter kind, frame count, first/last timestamp + span (ns), the set of channels seen, the set of subcarrier counts seen, mean quality score, the validation breakdown (accepted / degraded / recovered / rejected / pending), and the calibration version if any.
  3. Flag anything suspicious: many rejected (bad source or wrong profile), several distinct subcarrier counts (mixed legacy/HT frames — the window pipeline only aggregates consistent runs), channel = 0 (channel detection failed at the source), low mean quality.
  4. Natural next steps: /rvcsi-events <file> (run the detectors), /rvcsi-calibrate --in <file> (learn a baseline), /rvcsi-record … if you need to re-transcode.
Changes

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.

  1. 8d ago First seen · 14 lines · 28 tokens per session scan A 6d967cfe47bd

Subscribe to this mod's changes

rvcsi-inspect is a command published in the GitHub repository ruvnet/rvcsi (22 stars, last pushed 15d ago), licensed Apache-2.0. It adds 28 tokens to every session and 299 once invoked, about $0.0001 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-08-30.