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.
git 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/migrate)<a href="https://agentmods.dev/commands/jhlee0409/claude-plugins/migrate"><img src="https://agentmods.dev/badge/commands/jhlee0409/claude-plugins/migrate/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.
<a href="https://agentmods.dev/commands/jhlee0409/claude-plugins/migrate"><img src="https://agentmods.dev/badge/commands/jhlee0409/claude-plugins/migrate.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.06029 |
| Opus 5.5 | $0.00003 | $0.02412 |
| Sonnet 5.5 | $0.00002 | $0.01206 |
| Haiku 4.5 | $0.00001 | $0.00603 |
Grade A, and why
migrate 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.
How it starts
The opening of the file, as written. The whole thing — 786 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fsdarch:migrate
기존 프로젝트를 FSD 아키텍처로 마이그레이션하는 분석 및 가이드를 제공합니다.
Prerequisites
- 프로젝트 루트 디렉토리에서 실행
- 기존 소스 코드 존재
- (권장)
/fsdarch:init실행 완료
EXECUTION INSTRUCTIONS
When /fsdarch:migrate is invoked, Claude MUST perform these steps in order:
- Analyze current structure - Scan existing project directories
- Classify modules - Categorize code into FSD layers
- Detect dependencies - Map imports between modules
- Generate migration plan - Create phased migration guide
- Output report - Display analysis and recommendations
Flow Overview
┌───────────────────────────────────────────────────────────────┐
│ /fsdarch:migrate │
├───────────────────────────────────────────────────────────────┤
│ Step 1. Analyze current structure │
│ ├─ Find source directory │
│ ├─ Load layerAliases from config (if exists) │
│ ├─ List all directories and files │
│ └─ Categorize by common patterns │
│ │
│ Step 2. Classify modules into FSD layers │
│ ├─ components/* → shared/ui, widgets, features │
│ ├─ hooks/* → features/model, entities/model │
│ ├─ utils/* → shared/lib │
│ ├─ services/* → shared/api, entities/api │
│ └─ pages/* → pages layer │
│ │
│ Step 3. Detect dependencies │
│ ├─ Parse import statements │
│ ├─ Build dependency graph │
│ └─ Identify circular dependencies │
│ │
│ Step 3.5. Apply layer aliases (if configured) │
│ └─ Resolve target paths: app→core, pages→views, etc. │
│ │
│ Step 4. Generate migration plan (with aliased paths) │
│ ├─ Phase 1: Create FSD structure │
│ ├─ Phase 2: Migrate shared layer │
│ ├─ Phase 3: Migrate entities │
│ ├─ Phase 4: Migrate features │
│ ├─ Phase 5: Migrate widgets │
│ ├─ Phase 6: Migrate pages │
│ └─ Phase 7: Cleanup │
│ │
│ Step 5. Output migration report │
│ ├─ Structure analysis │
│ ├─ Layer distribution │
│ ├─ Risk assessment │
│ └─ Recommendations │
└───────────────────────────────────────────────────────────────┘
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 · 786 lines · 8 tokens per session scan A 3ff851878822
migrate is a command published in the GitHub repository jhlee0409/claude-plugins (4 stars, last pushed 9mo ago), licensed MIT. It adds 8 tokens to every session and 6,029 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.
Other commands, from other repositories
skill-refresh
You are running inside a headless Claude Code session in the neo4j-skills repository. Goal: scan Neo4j release notes and deprecation pages, then update any SKILL.md and references/ files that are stale, outdated, or missing new features. Open no PRs or commits — output only file edits. The workflow will handle git and…
speckit.md-doctor.drift
Re-evaluate since the last run: compute the git/.memsearch/TDD delta, re-score previously graded files in light of what changed, and report which past suggestions were resolved or are now stale/false.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.
speckit.gym.drop
Record a drop card from a mis-fire. A mis-fire is not a mistake to punish — it is a discovery to keep. Drop cards capture what was done, what was expected, and what happened, persisted to the configured redundant stores (default /drops/ plus the extension's append-only .drop-ledger.md).
speckit.spec-stats.open
On-demand view of everything not complete: what stage each is stuck at, what the immediate next artifact/command is, oldest-untouched first, stale warnings past staleafterdays.
new-month
Start a new month for a brand: folder and settings; a calendar to load -> parse-calendar; ideas -> ideate-month. "start a new month for this brand".