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 plugins/ruvnet/ruview/marketplace/plugin marketplace add ruvnet/RuViewgit clone --depth 1 https://github.com/ruvnet/RuViewGrade A, and why
ruview 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 yesterday.
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.
What it actually says
{
"name": "ruview",
"description": "RuView Marketplace: Claude Code + Codex plugins for WiFi sensing — configuration, applications, model training, and onboarding, from practical to advanced",
"owner": {
"name": "ruvnet",
"url": "https://github.com/ruvnet/RuView"
},
"plugins": [
{
"name": "ruview",
"source": "./plugins/ruview",
"description": "End-to-end RuView toolkit: getting started, ESP32 hardware setup, configuration, sensing applications (presence / vitals / pose / sleep / MAT), camera-free + camera-supervised model training, advanced multistatic sensing, CLI / API / WASM, mmWave radar, and witness verification"
}
]
}
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.
- yesterday First seen · 16 lines scan A b5daf01db8cf
ruview is a plugin published in the GitHub repository ruvnet/RuView (92,079 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
chmonitor
Specialized assistance for the chmonitor dashboard - a real-time monitoring dashboard for ClickHouse clusters.
cardputer
Hardware reference and firmware-development helper for the M5Stack Cardputer family. Covers pinout, I2C peripherals (TCA8418 keyboard, BMI270 IMU, ES8311 codec), display, Grove/EXT ports, battery behavior, and setup for Arduino IDE, PlatformIO, ESP-IDF, and UIFlow2. Includes cap accessories that snap onto the…
zapi-mcp
Zabbix API for Claude Code, via an API user. Investigate active problems, hosts, and item values, get a one-shot dailybrief health check, acknowledge problems, and open maintenance windows. Site-specific dailybrief categories (DHCP pool usage, SNAT usage, core-network, …) need a local ZABBIXCATEGORIESINI file that.
alihassanml
Developer tooling for Claude Code.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.