agentmods.dev

analyze

A project-analysis command that examines structure, architecture, dependencies, testing, documentation, and likely technical debt.

In plain words
What is it for?
Use it for a full or targeted architecture review, including component mapping, dependency tracing, quality assessment, and recommendations.
Why use it?
It turns a broad codebase review into a defined assessment of how the project is organized and where risks or improvements may lie.

Command

85 1mo ago A scan 5 tokens original MIT
View the source file stefan-jansen/claude-code-toolkit
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/stefan-jansen/claude-code-toolkit/analyze
Clone the repo
git clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkit
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 398 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.

ModelPer sessionOnce invoked
Fable 5 $0.00005 $0.00398
Opus 5 $0.00003 $0.00199
Sonnet 5 $0.00001 $0.00080
Haiku 4.5 $0.00001 $0.00040

Measured 2d ago against content hash 5331b8e59716, 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/development/commands/analyze.md · 60 lines

What it actually says

Analyze Project

Deep codebase analysis for architecture, patterns, and improvement opportunities.

Input: $ARGUMENTS

Flags

  • --with-thinking: Use Sequential Thinking for complex analysis
  • --semantic: Use Serena for symbol-level understanding

Process

  1. Determine Scope

    • No args: Comprehensive review
    • Focus area: Targeted examination
    • @document: Requirements-based analysis

  2. Project Assessment

    • Language/framework detection
    • Architecture style (monolith, microservices, layered)
    • Code organization and patterns
    • Testing approach and coverage
    • Documentation state
    • Technical debt indicators

  3. Deep Analysis

    • Map core components and responsibilities
    • Trace dependency relationships
    • Identify design patterns in use
    • Find integration points and boundaries
    • Assess code quality and maintainability

  4. Semantic Analysis (with Serena)

    • Symbol-level component mapping
    • Actual import/dependency tracking
    • Interface and API surface analysis
    • Cross-reference usage patterns

  5. Generate Report

    • Architecture overview diagram (ASCII/Mermaid)
    • Component inventory
    • Quality assessment
    • Improvement recommendations
    • Risk areas

Output

Write findings to exploration.md or return structured summary:

  • Architecture type and patterns
  • Key components and relationships
  • Quality metrics
  • Actionable recommendations
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.

  1. 2d ago First seen · 60 lines · 5 tokens per session scan A 5331b8e59716

Subscribe to this mod's changes

analyze is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (85 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 398 once invoked, about $0.0000 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.

Planningagentsanthropicclaude-codecoding-agentsframeworkplugins
Related

Other commands, from other repositories

ctx

Search agent history or trace code to its original agent session.

ctxrs/ctx · 11 tokens

enrich

Enrich project memory by mining 100 recently merged PRs: extracts decisions, conventions, gotchas, and architectural facts from PR discussions, review comments, and PR bodies.

RashadAnsari/myagents · 34 tokens

reportloop

Interactively walk through all issues in REVIEWREPORT.md: explains each issue, asks to fix or skip, handles follow-up questions, and applies fixes one by one in severity order.

RashadAnsari/myagents · 36 tokens

pr-review

Review a GitHub pull request: analyzes changed files to select relevant reviewers, loads project and user memory, runs reviewers in parallel, lets the user pick which findings to post, then submits the review on behalf of the user via gh CLI.

RashadAnsari/myagents · 47 tokens

a11y

Audit and fix WCAG AA compliance — semantic HTML, ARIA, keyboard, contrast, reduced-motion.

aneja5/forge-skills · 20 tokens

components

Build component catalog with props, states, and accessibility.

aneja5/forge-skills · 10 tokens