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 commands/superclaude-org/superclaude_framework/analyzegit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWrote 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/commands/superclaude-org/superclaude_framework/analyze)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/analyze"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/analyze.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.00017 | $0.00615 |
| Opus 5 | $0.00009 | $0.00308 |
| Sonnet 5 | $0.00003 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/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: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:analyze
# Multi-domain analysis of entire project
# Generates comprehensive report with key findings and roadmap
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.
- 4d ago First seen · 89 lines · 17 tokens per session scan A f39442633827
analyze is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,866 stars, last pushed 14d ago), licensed MIT. It adds 17 tokens to every session and 615 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
dashboard
Running banco with no subcommand opens a full-screen, read-only dashboard for the current project.
tidy
Reports module data that the current configuration no longer backs — repositories dropped from a provider, task trees whose syncing was turned off, and local items you may want to retire. The output is JSON, intended for agents (see the tidy skill).
check
Scans the project directory for content that does not belong to any module and reports it.
troubleshoot
Diagnose and resolve issues in code, builds, deployments, and system behavior.
sync
Pulls data from configured remote providers and writes it to the local filesystem.
analyze
Comprehensive code analysis across quality, security, performance, and architecture domains.