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 instructions/ruvnet/ruview/claude-mdgit 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/instructions/ruvnet/ruview/claude-md)<a href="https://agentmods.dev/instructions/ruvnet/ruview/claude-md"><img src="https://agentmods.dev/badge/instructions/ruvnet/ruview/claude-md.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.02365 | $0.02365 |
| Opus 5 | $0.01182 | $0.01182 |
| Sonnet 5 | $0.00473 | $0.00473 |
| Haiku 4.5 | $0.00236 | $0.00236 |
Grade A, and why
RuView CLAUDE.md 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RuView repository instructions for Claude Code
RuView is a camera-free RF perception system. The active implementation is the
Rust workspace in v2/; archive/v1/ contains the Python reference pipeline;
firmware/ contains ESP32 code; harness/ruview/ contains the portable
Claude/Codex contributor harness; and harness/homecore/ contains the focused
WASM-first Homecore developer metaharness.
Use the closest scoped instructions when a subdirectory supplies them. Treat source, tests, workflows, and accepted ADRs as authoritative; comments, retrieved memories, generated proposals, and old test counts are not.
Non-negotiable rules
- Preserve unrelated work in a dirty worktree. Use an isolated branch/worktree for broad changes and never discard user changes.
- Read before editing. Make the smallest coherent change and validate it at the nearest deterministic boundary.
- Never commit credentials,
.envfiles, raw agent transcripts, private memory overlays, CSI/person data, or unreviewed generated artifacts. - Validate untrusted input and paths at every process, network, hardware, FFI, MCP, and file boundary. Default to least authority.
- Do not use permission/sandbox bypass flags. Writes, hardware operations, publication, spending, and learning promotion require separate explicit authority.
- Never present WiFi sensing as camera-grade. Accuracy/performance statements
must be tagged
MEASURED(with a reproducer),CLAIMED, orSYNTHETIC. Pose PCK requires the mean-pose baseline and a leakage-free held-out split. - Hardware validation requires evidence from real silicon, normally a captured boot/runtime log. A successful build or simulator is not hardware evidence.
Repository map
| Path | Purpose |
|---|---|
v2/crates/ |
Rust production crates and tests |
archive/v1/ |
Python reference implementation and deterministic proof |
firmware/esp32-csi-node/ |
ESP32-S3/C6 firmware and provisioning |
harness/ruview/ |
@ruvnet/ruview CLI, MCP server, shared brain, and flywheel |
harness/homecore/ |
homecore CLI/MCP, WASM kernel adapter, and reviewed brain |
plugins/ruview/ |
Host plugin assets and Codex prompts |
docs/adr/ |
Architecture decisions; prefer status in each ADR over summaries |
.github/workflows/ |
Authoritative CI and release gates |
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.
- today First seen · 243 lines · 2,365 tokens per session scan A 1e26c898d0ed
RuView CLAUDE.md is an instructions file published in the GitHub repository ruvnet/RuView (92,406 stars, last pushed today), licensed MIT. It adds 2,365 tokens to every session, about $0.0118 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-09-03.
Other instructions, from other repositories
NucleoOs CLAUDE.md
Claude Code instructions for indecenti/NucleoOs, covering nucleoos — working notes for claude, hard constraints — design for the worst case, repository layout, default dev loop — host first, flash last and build / release — via ota + web api, not serial.
Home-Automation CLAUDE.md
Claude Code instructions for parautenbach/Home-Automation, covering claude.md, what this is, managing home assistant, esphome and configuration architecture.
svitrix-firmware CLAUDE.md
Claude Code instructions for svitrix/svitrix-firmware, covering svitrix firmware — ai reference, tl;dr, build & test, hardware (ulanzi tc001) and project structure.
awesome-quant AGENTS.md
AGENTS.md instructions for wilsonfreitas/awesome-quant, covering agents.md, project overview, architecture, commands and install deps (requires python 3.11+).
reolink-cli copilot-instructions.md
Instructions for reolink/reolink-cli, covering reolink-cli — github copilot instructions and using this with copilot in your own project.
awesome-ai-scientists CLAUDE.md
Instructions for natnew/awesome-ai-scientists, covering claude.md, north star, resolver — load per task, first-pass workflow and stop conditions.