What is deep-analysis?

A command that performs a broad investigation of a codebase, from its files and dependencies to its architecture, coding conventions, core behavior, and integrations.

Use it to map project structure, identify languages and frameworks, understand module boundaries and workflows, and locate important APIs, databases, and external services.

It creates a fuller picture of how an unfamiliar project is organized and works before changes or troubleshooting begin.

How tomdwipo/claude-soul configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tomdwipo/claude-soul. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tomdwipo/claude-soul/main/.claude/commands/deep-analysis.md

Clone the repo

git clone --depth 1 https://github.com/tomdwipo/claude-soul

Made for: Claude Code.

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/tomdwipo/claude-soul/deep-analysis/github.svg)](https://agentmods.dev/commands/tomdwipo/claude-soul/deep-analysis)

Your own site

<a href="https://agentmods.dev/commands/tomdwipo/claude-soul/deep-analysis"><img src="https://agentmods.dev/badge/commands/tomdwipo/claude-soul/deep-analysis/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/tomdwipo/claude-soul/deep-analysis"><img src="https://agentmods.dev/badge/commands/tomdwipo/claude-soul/deep-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 462 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.00000	$0.00462
Opus 5.5	$0.00000	$0.00185
Sonnet 5.5	$0.00000	$0.00092
Haiku 4.5	$0.00000	$0.00046

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

Security

Grade A, and why

deep-analysis 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.

.claude/commands/deep-analysis.md · 69 lines

How it starts

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

Deep Codebase Understanding

Perform comprehensive analysis of: $ARGUMENTS (or entire codebase if no specific area mentioned)

Phase 1: Architecture Discovery

Project Structure Analysis
- Map directory structure and organization patterns
- Identify main entry points and configuration files
- Understand build systems, package managers, dependencies
Technology Stack Identification
- Programming languages and versions
- Frameworks, libraries, and their versions
- Database systems, APIs, external services
- Development and deployment tools

Phase 2: Code Pattern Analysis

Design Patterns & Architecture
- Identify architectural patterns (MVC, microservices, etc.)
- Code organization principles
- Module boundaries and responsibilities
- Data flow and control flow patterns
Coding Conventions & Standards
- Naming conventions
- Code style and formatting rules
- Error handling patterns
- Testing strategies and patterns

Phase 3: Deep Code Understanding

Core Functionality Mapping
- Main features and business logic
- Key algorithms and data structures
- Critical paths and workflows
- Integration points and APIs
Dependencies & Relationships
- Inter-module dependencies
- External service integrations
- Database schema and relationships
- Configuration management

Phase 4: Context Building

Historical Context
- Recent commits and change patterns
- TODO comments and known issues
- Documentation and inline comments
- Test coverage and quality metrics
Runtime Behavior
- Environment configurations
- Deployment patterns
- Monitoring and logging setup
- Performance considerations

Execution Method:

Use bash commands /search for searching on qdrant vector database, grep, and read tools extensively
Analyze package.json, requirements.txt, Gemfile, etc.
Read README, docs, and configuration files
Examine test files for behavior understanding
Review recent git history for context

Read the full file on GitHub · 69 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 · 69 lines · 0 tokens per session scan A 48c5ec6acf80

Subscribe to this mod's changes

deep-analysis is a command published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 462 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.

Research

deep-analysis next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
deep-analysistomdwipo/claude-soul	Command	24	2mo ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

claude-soul: Command for Claude Code