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.
curl -O https://raw.githubusercontent.com/tomdwipo/claude-soul/main/.claude/commands/deep-analysis.mdgit clone --depth 1 https://github.com/tomdwipo/claude-soulWrote 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/tomdwipo/claude-soul/deep-analysis)<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="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.1 | $0.00000 | $0.00462 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
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 7d 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 — 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
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.
- 7d ago First seen · 69 lines · 0 tokens per session scan A 48c5ec6acf80
deep-analysis is a command published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed 1mo 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.