A command for investigating an unfamiliar codebase and explaining how its parts fit together. It searches code, follows imports and dependencies, and reports where relevant implementations are located.

Use it to find features such as registration or payments, trace a request from an API endpoint to a database, inspect authentication, analyse dependencies, or locate all uses of a pattern.

It reduces the time spent manually searching through files to understand architecture or trace a feature. It can also help locate the source of a bug or a repeated coding pattern.

analyze — Command by MadAppGang

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/madappgang/claude-code/analyze

Clone the repo

git clone --depth 1 https://github.com/MadAppGang/claude-code

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

When invoked 1,366 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.

Model	Per session	Once invoked
Fable 5	$0.00021	$0.01366
Opus 5	$0.00010	$0.00683
Sonnet 5	$0.00004	$0.00273
Haiku 4.5	$0.00002	$0.00137

Measured 2d ago against content hash a40477023797, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

plugins/code-analysis/commands/analyze.md · 197 lines

How it starts

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

Mission

Launch the codebase-detective agent to perform comprehensive code analysis, investigation, and navigation across complex codebases. This command helps understand how code works, find specific implementations, trace functionality flow, and analyze architectural patterns.

Analysis Request

$ARGUMENTS

When to Use This Command

Use /analyze when you need to:

Understand Architecture: How is authentication implemented? What's the database layer structure?
Find Implementations: Where is the user registration logic? Which file handles payments?
Trace Functionality: Follow the flow from API endpoint to database
Debug Issues: Why isn't the login working? Where is this error coming from?
Find Patterns: Where are all the API calls made? What components use Redux?
Analyze Dependencies: What uses this service? Where is this utility imported?

How It Works

This command launches the codebase-detective agent, which:

Uses semantic code search (claudemem CLI) when available
Falls back to standard grep/find/rg tools when needed
Traces imports and dependencies across files
Analyzes code structure and patterns
Provides exact file locations with line numbers
Explains code relationships and flow

Instructions

Step 1: Understand the Request

Parse the user's analysis request from $ARGUMENTS:

What are they trying to understand?
What specific code/functionality are they looking for?
What's the context (debugging, learning, refactoring)?

Step 2: Launch codebase-detective Agent

Use the Task tool to launch the agent:

Task(
  subagent_type: "code-analysis:detective",
  description: "Analyze codebase for [brief description]",
  prompt: `
    Investigate the following in the codebase:

    [User's analysis request from $ARGUMENTS]

    Working directory: [current working directory]

    Please provide:
    1. Exact file locations with line numbers
    2. Code snippets showing the implementation
    3. Explanation of how the code works
    4. Related files and dependencies
    5. Code flow/architecture diagram if complex

    Use semantic search (claudemem CLI) if available, otherwise
    use grep/ripgrep/find for pattern matching.
  `
)

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

2d ago First seen · 197 lines · 21 tokens per session scan A a40477023797

Subscribe to this mod's changes

analyze is a command published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 1,366 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.

Debugging

analyze