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/full-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/full-analysis)<a href="https://agentmods.dev/commands/tomdwipo/claude-soul/full-analysis"><img src="https://agentmods.dev/badge/commands/tomdwipo/claude-soul/full-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.01043 |
| Opus 5 | $0.00000 | $0.00522 |
| Sonnet 5 | $0.00000 | $0.00209 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
full-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 8d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete Codebase Analysis
Perform comprehensive analysis of the entire codebase: $ARGUMENTS
Phase 1: Project Foundation & Structure
1.1 Project Overview
Get project basics
pwd ls -la find . -maxdepth 2 -type d | head -20 1.2 Technology Stack Discovery
Read package.json, requirements.txt, Gemfile, pom.xml, Cargo.toml, go.mod Identify programming languages used List all dependencies and their versions Understand build tools and configuration
1.3 Project Structure Mapping
Map all major directories and their purposes Identify configuration directories Locate documentation, tests, and build files Find entry points and main application files
Phase 2: Architecture & Design Analysis 2.1 System Architecture
Identify architectural patterns (MVC, microservices, layered, etc.) Map component relationships and dependencies Understand data flow and control flow Identify system boundaries and interfaces
2.2 Code Organization
Analyze module structure and organization Identify separation of concerns Map business logic distribution Understand code layering (presentation, business, data)
Phase 3: Deep Code Analysis 3.1 Core Functionality Inventory bash# Find all main files by language find . -name ".js" -o -name ".ts" -o -name ".py" -o -name ".java" -o -name ".go" -o -name ".rs" -o -name "*.php" | grep -v node_modules | grep -v vendor | wc -l 3.2 Critical Components Analysis
Models/Entities: Data structures and business objects Controllers/Handlers: Request processing and routing Services/Business Logic: Core application logic Views/Templates: UI components and rendering Utilities/Helpers: Shared functionality Configuration: Environment and app settings
3.3 Integration Points
Database connections and ORM usage External API integrations Authentication and authorization systems Caching mechanisms Message queues and event systems
Phase 4: Code Quality & Patterns Analysis 4.1 Coding Conventions
Naming conventions (variables, functions, classes, files) Code formatting and style patterns Comment and documentation patterns Import/export organization
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.
- 8d ago First seen · 179 lines · 0 tokens per session scan A e4cdad983a93
full-analysis is a command published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,043 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.