analyzer

A code and data analysis command that examines files in batches and produces detailed reports. It can inspect performance, memory use, dependencies, and data patterns.

In plain words
What is it for?
Use it to analyze a codebase, profile performance, inspect memory usage, map dependencies, or find patterns across multiple files.
Why use it?
It reduces the manual work of reviewing many files and collecting performance information. The results can help identify problems and possible improvements.

Command for Claude Code

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/analyzer
Clone the repo
git clone --depth 1 https://github.com/ruvnet/RuView

Made for: Claude Code.

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 282 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 $0.00000 $0.00282
Opus 5 $0.00000 $0.00141
Sonnet 5 $0.00000 $0.00056
Haiku 4.5 $0.00000 $0.00028

Measured yesterday against content hash bd6a184d3fcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

  • analyzer — 100% identical, 0 lines differ
  • analyzer — 100% identical, 0 lines differ
  • analyzer — 100% identical, 0 lines differ
  • analyzer — 100% identical, 0 lines differ
.claude/commands/sparc/analyzer.md · 52 lines

What it actually says

SPARC Analyzer Mode

Purpose

Deep code and data analysis with batch processing capabilities.

Activation

Option 1: Using MCP Tools (Preferred in Claude Code)

mcp__claude-flow__sparc_mode {
  mode: "analyzer",
  task_description: "analyze codebase performance",
  options: {
    parallel: true,
    detailed: true
  }
}

Option 2: Using NPX CLI (Fallback when MCP not available)

# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run analyzer "analyze codebase performance"

# For alpha features
npx claude-flow@alpha sparc run analyzer "analyze codebase performance"

Option 3: Local Installation

# If claude-flow is installed locally
./claude-flow sparc run analyzer "analyze codebase performance"

Core Capabilities

  • Code analysis with parallel file processing
  • Data pattern recognition
  • Performance profiling
  • Memory usage analysis
  • Dependency mapping

Batch Operations

  • Parallel file analysis using concurrent Read operations
  • Batch pattern matching with Grep tool
  • Simultaneous metric collection
  • Aggregated reporting

Output Format

  • Detailed analysis reports
  • Performance metrics
  • Improvement recommendations
  • Visualizations when applicable
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. yesterday First seen · 52 lines · 0 tokens per session scan A bd6a184d3fcf

Subscribe to this mod's changes

analyzer is a command published in the GitHub repository ruvnet/RuView (92,079 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 282 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.