A command that examines a Feature-Sliced Design project, an approach for organizing a frontend codebase into defined layers and feature areas, and creates a health report.

Analyzing an FSD project, checking layer and slice dependencies, calculating a health score, and generating an incremental report.

It checks the project structure, import boundaries, and other criteria so architectural problems are easier to find.

analyze — Command for Claude Code by jhlee0409/claude-plugins

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.

Clone the repo

git clone --depth 1 https://github.com/jhlee0409/claude-plugins

Made for: Claude Code.

Or install fsdarch, the plugin that ships this one along with the rest of its 4 skills, 6 commands.

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/jhlee0409/claude-plugins/analyze/github.svg)](https://agentmods.dev/commands/jhlee0409/claude-plugins/analyze)

Your own site

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

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

When invoked 4,542 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.00009	$0.04542
Opus 5.5	$0.00004	$0.01817
Sonnet 5.5	$0.00002	$0.00908
Haiku 4.5	$0.00001	$0.00454

Measured 1mo ago against content hash 588488939591, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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/fsd-architect/commands/analyze.md · 615 lines

How it starts

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

/fsdarch:analyze

현재 FSD 프로젝트 구조를 분석하고 상세 리포트를 생성합니다.

Prerequisites

.fsd-architect.json 설정 파일 존재 (없으면 /fsdarch:init 먼저 실행)

EXECUTION INSTRUCTIONS

When /fsdarch:analyze is invoked, Claude MUST perform these steps in order:

Load configuration - Read .fsd-architect.json (error E104 if missing)
Check cache - Use skill: cache-manager for incremental analysis
Use skill: layer-detector - Scan all layers and slices
Use skill: boundary-checker - Analyze import dependencies
Calculate health score - Score based on 5 criteria
Generate report - Display formatted analysis results
Update cache - Save analysis results for incremental updates

Flow Overview

┌───────────────────────────────────────────────────────────────┐
│                      /fsdarch:analyze                         │
├───────────────────────────────────────────────────────────────┤
│  1. Load .fsd-architect.json                                  │
│     ├─ Not found → Error E104, suggest /fsdarch:init          │
│     └─ Found → Continue                                       │
│                                                               │
│  2. Check cache (unless --force)                              │
│     ├─ Valid cache exists → Use incremental analysis          │
│     └─ No cache / stale → Full scan                           │
│                                                               │
│  3. Invoke skill: layer-detector                              │
│     → Scan all layers, slices, segments                       │
│     → Count files per layer/slice                             │
│                                                               │
│  4. Invoke skill: boundary-checker                            │
│     → Parse import statements                                 │
│     → Build dependency graph                                  │
│     → Detect violations (E201, E202, E203, E204, E205)        │
│                                                               │
│  5. Calculate health score (100 points)                       │
│     → Layer hierarchy (30%)                                   │
│     → Public API usage (25%)                                  │
│     → Slice isolation (20%)                                   │
│     → Naming consistency (15%)                                │
│     → Segment structure (10%)                                 │
│                                                               │
│  6. Display report with issues and recommendations            │
│                                                               │
│  7. Update .fsd-architect.cache.json                          │
└───────────────────────────────────────────────────────────────┘

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

1mo ago First seen · 615 lines · 9 tokens per session scan A 588488939591

Subscribe to this mod's changes

analyze is a command published in the GitHub repository jhlee0409/claude-plugins (4 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 4,542 once invoked, about $0.0000 per session on Opus 5.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-31.

Claude Code Debugging Frontend api-codegen claude-plugin code-generator openapi react-query

fix-issue

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…

yonatangross/orchestkit · 82 tokens

ci-sentinel

Daily autonomous classifier for failing PRs across your repos. Runs /ci-debug headless against every open PR with red required checks, posts the verdict as a collapsed PR comment, and appends to a per-repo .sentinel/ledger.jsonl. v1 is propose-don't-apply — NEVER auto-pushes a fix. Use when you're tired of /status…

yonatangross/orchestkit · 94 tokens

ci-debug

Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…

yonatangross/orchestkit · 92 tokens

analyze