A command that finds a named component in a codebase, examines its structure and quality, and produces findings with recommendations.

Use it to review one named component and receive a summary, identified problems, and suggested improvements.

It reduces the manual work of locating a component and checking it for patterns, quality problems, and possible issues.

analyze — Command for Claude Code by C0ntr0lledCha0s

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/C0ntr0lledCha0s/claude-code-plugin-automations

Made for: Claude Code.

Or install my-standard-plugin, the plugin that ships this one along with the rest of its 2 commands, 1 agent.

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/c0ntr0lledcha0s/claude-code-plugin-automations/analyze/github.svg)](https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/analyze)

Your own site

<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/analyze"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/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/c0ntr0lledcha0s/claude-code-plugin-automations/analyze"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 492 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.00007	$0.00492
Opus 5.5	$0.00003	$0.00197
Sonnet 5.5	$0.00001	$0.00098
Haiku 4.5	$0.00001	$0.00049

Measured 1mo ago against content hash fd6b8e593d1a, 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 1mo 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.

claude-component-builder/skills/building-plugins/templates/standard-plugin-template/commands/analyze.md · 103 lines

How it starts

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

Analyze Command

Perform comprehensive analysis of a component and provide actionable recommendations.

Usage

/my-standard-plugin:analyze [component-name]

What This Command Does

Locate Component: Find the specified component in the codebase
Analyze Structure: Examine code structure and patterns
Check Quality: Assess code quality and best practices
Generate Report: Provide detailed findings and recommendations

Parameters

component-name: (Required) The name of the component to analyze

Implementation Steps

Step 1: Validate Input

Check if component-name is provided:

If $1 is empty:
  Ask user: "Which component would you like to analyze?"
  Exit

Step 2: Find Component

Search for the component in the codebase:

Use Grep to find files matching the component name
Verify the component exists

Step 3: Analyze Component

Read and analyze relevant files:

Check code structure
Identify patterns
Assess quality
Find potential issues

Step 4: Generate Report

Provide comprehensive findings:

Summary: Brief overview
Findings: Detailed analysis
Issues: Problems identified
Recommendations: Actionable improvements

Example

/my-standard-plugin:analyze authentication

Expected Output:

🔍 Analyzing 'authentication' component...

📊 ANALYSIS RESULTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

✅ Strengths:
- Well-structured code
- Good test coverage

⚠️  Issues Found:
- Missing input validation in login.ts:45
- Deprecated method used in auth.ts:78

💡 Recommendations:
1. Add input validation for user credentials
2. Update to use new authentication API
3. Consider adding rate limiting

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Error Handling

If component not found: Suggest similar component names
If access denied: Check permissions
If analysis fails: Provide error details

Notes

Analysis is read-only (no modifications)
Results are displayed in terminal
Consider using the example-agent for deeper analysis

Read the full file on GitHub · 103 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.

1mo ago First seen · 103 lines · 7 tokens per session scan A fd6b8e593d1a

Subscribe to this mod's changes

analyze is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 492 once invoked, about $0.0000 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-31.

Code review

analyze