A command for reviewing a codebase across code quality, security, speed, and system design. It examines project files, rates findings by seriousness, and produces recommendations and reports.

Checking a whole project or selected component, focusing on quality, security, performance, or architecture. It can produce quick or detailed results as text, JSON, or a report.

It brings common code-review checks into one assessment, making it easier to find security risks, slow parts, design problems, and technical debt.

analyze — Command for Claude Code by SuperClaude-Org

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/SuperClaude-Org/SuperClaude_Plugin

Made for: Claude Code.

Or install sc, the plugin that ships this one along with the rest of its 32 commands, 20 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-analyze/github.svg)](https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-analyze)

Your own site

<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-analyze"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-analyze/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-analyze"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 693 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.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.00693
Opus 5.5	$0.00007	$0.00277
Sonnet 5.5	$0.00003	$0.00139
Haiku 4.5	$0.00002	$0.00069

Measured 2mo ago against content hash f03613e5a2fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

commands/sc-analyze.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/sc:sc:sc:analyze - Code Analysis and Quality Assessment

Triggers

Code quality assessment requests for projects or specific components
Security vulnerability scanning and compliance validation needs
Performance bottleneck identification and optimization planning
Architecture review and technical debt assessment requirements

Usage

/sc:sc:analyze [target] [--focus quality|security|performance|architecture] [--depth quick|deep] [--format text|json|report]

Behavioral Flow

Discover: Categorize source files using language detection and project analysis
Scan: Apply domain-specific analysis techniques and pattern matching
Evaluate: Generate prioritized findings with severity ratings and impact assessment
Recommend: Create actionable recommendations with implementation guidance
Report: Present comprehensive analysis with metrics and improvement roadmap

Key behaviors:

Multi-domain analysis combining static analysis and heuristic evaluation
Intelligent file discovery and language-specific pattern recognition
Severity-based prioritization of findings and recommendations
Comprehensive reporting with metrics, trends, and actionable insights

Tool Coordination

Glob: File discovery and project structure analysis
Grep: Pattern analysis and code search operations
Read: Source code inspection and configuration analysis
Bash: External analysis tool execution and validation
Write: Report generation and metrics documentation

Key Patterns

Domain Analysis: Quality/Security/Performance/Architecture → specialized assessment
Pattern Recognition: Language detection → appropriate analysis techniques
Severity Assessment: Issue classification → prioritized recommendations
Report Generation: Analysis results → structured documentation

Examples

Comprehensive Project Analysis

/sc:sc:analyze
# Multi-domain analysis of entire project
# Generates comprehensive report with key findings and roadmap

Read the full file on GitHub · 98 lines

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.

2mo ago First seen · 98 lines · 17 tokens per session scan A f03613e5a2fa

Subscribe to this mod's changes

analyze is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 693 once invoked, about $0.0001 per session on Opus 5.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.

Code review Debugging utility

analyze