repo-analyze

repo-analyze is a command for Claude Code from ruvnet/RuView. It costs 0 tokens per session (157 once invoked), scanned A, original, MIT.

A command that examines a GitHub repository and provides AI-based analysis. It can focus on areas such as issues, pull requests, code, or commits.

In plain words
What is it for?
Use it for a basic or detailed repository review, or limit the analysis to selected areas such as issues and pull requests.
Why use it?
It gathers information from different parts of a repository so you can review its state without checking each area separately.

Command for Claude Code

Written for Claude Code: installed under .claude/.

About the project

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.

ruvnet/RuView · 92,558 stars · on GitHub · cognitum.one

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.

agentmods
npx agentmods add commands/ruvnet/ruview/repo-analyze
Clone the repo
git clone --depth 1 https://github.com/ruvnet/RuView

Made for: Claude Code.

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 repo-analyze

README.md
[![agentmods](https://agentmods.dev/badge/commands/ruvnet/ruview/repo-analyze.svg)](https://agentmods.dev/commands/ruvnet/ruview/repo-analyze)
Your own site
<a href="https://agentmods.dev/commands/ruvnet/ruview/repo-analyze"><img src="https://agentmods.dev/badge/commands/ruvnet/ruview/repo-analyze.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 157 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00000 $0.00157
Opus 5 $0.00000 $0.00078
Sonnet 5 $0.00000 $0.00031
Haiku 4.5 $0.00000 $0.00016

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

Security

Grade A, and why

repo-analyze 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 6d 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

.claude/commands/github/repo-analyze.md · 26 lines

What it actually says

repo-analyze

Deep analysis of GitHub repository with AI insights.

Usage

npx claude-flow github repo-analyze [options]

Options

  • --repository <owner/repo> - Repository to analyze
  • --deep - Enable deep analysis
  • --include <areas> - Include specific areas (issues, prs, code, commits)

Examples

# Basic analysis
npx claude-flow github repo-analyze --repository myorg/myrepo

# Deep analysis
npx claude-flow github repo-analyze --repository myorg/myrepo --deep

# Specific areas
npx claude-flow github repo-analyze --repository myorg/myrepo --include issues,prs
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. 6d ago First seen · 26 lines · 0 tokens per session scan A 7c57c22d09ee

Subscribe to this mod's changes

repo-analyze is a command published in the GitHub repository ruvnet/RuView (92,558 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 157 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.