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.
npx agentmods add commands/jhlee0409/claude-plugins/analyzegit clone --depth 1 https://github.com/jhlee0409/claude-pluginsWrote 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/jhlee0409/claude-plugins/analyze)<a href="https://agentmods.dev/commands/jhlee0409/claude-plugins/analyze"><img src="https://agentmods.dev/badge/commands/jhlee0409/claude-plugins/analyze.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 | $0.00009 | $0.04542 |
| Opus 5 | $0.00005 | $0.02271 |
| Sonnet 5 | $0.00002 | $0.00908 |
| Haiku 4.5 | $0.00001 | $0.00454 |
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 3d 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 — 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 │
└───────────────────────────────────────────────────────────────┘
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.
- 3d ago First seen · 615 lines · 9 tokens per session scan A 588488939591
analyze is a command published in the GitHub repository jhlee0409/claude-plugins (4 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 4,542 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-31.
Other commands, from other repositories
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
save
Save this conversation as a new or existing reusable context.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
delegate
Delegate a coding task to the Cursor CLI agent (Composer by default).