Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jhlee0409/claude-pluginsnpx agentmods add commands/jhlee0409/claude-plugins/scaffoldWrote 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/scaffold)<a href="https://agentmods.dev/commands/jhlee0409/claude-plugins/scaffold"><img src="https://agentmods.dev/badge/commands/jhlee0409/claude-plugins/scaffold/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/scaffold"><img src="https://agentmods.dev/badge/commands/jhlee0409/claude-plugins/scaffold.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.00010 | $0.01911 |
| Opus 5.5 | $0.00004 | $0.00764 |
| Sonnet 5.5 | $0.00002 | $0.00382 |
| Haiku 4.5 | $0.00001 | $0.00191 |
Grade A, and why
scaffold 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fsdarch:scaffold
새 슬라이스 또는 세그먼트 보일러플레이트를 생성합니다. 프로젝트 패턴을 학습하여 일관된 스타일로 코드를 생성합니다.
Syntax
/fsdarch:scaffold <layer> <slice-name> [segment]
Prerequisites
.fsd-architect.json설정 파일 존재
Arguments
| Argument | Description | Example |
|---|---|---|
layer |
FSD 레이어 (entities, features, widgets, pages) | features |
slice-name |
슬라이스 이름 | auth |
segment |
(선택) 특정 세그먼트만 생성 | ui, model, api |
Execution Flow
Step 1: Validate Input
- 레이어 유효성 검사 (sliced layer인지 확인)
- 슬라이스 이름 검사 (기존 존재 여부)
- 세그먼트 유효성 검사 (SECURITY CRITICAL):
--segments플래그의 각 세그먼트에 대해 slice-generator의validateSegmentName()호출- Path traversal 공격 방지:
..,/,\금지 - Hidden directory 방지:
.으로 시작 금지 - 정규식 패턴
^[a-zA-Z][a-zA-Z0-9-_]*$준수 필수 - 검증 실패 시 E305 에러 반환
Step 2: Load Project Patterns
Use skill: layer-detector
-
설정 파일에서 패턴 로드:
- Naming convention (kebab-case, camelCase, etc.)
- 사용 중인 세그먼트
- Index file 패턴
-
동일 레이어의 기존 슬라이스 분석:
- 파일 구조 패턴
- Export 스타일
- 타입 정의 패턴
Step 3: Generate Structure
Use skill: slice-generator
- 슬라이스 디렉토리 생성
- 설정된 세그먼트별 파일 생성
- Public API (index.ts) 생성
Step 4: Apply Patterns
-
Naming Convention 적용
- 디렉토리명: 설정된 컨벤션 따름
- 파일명: 기존 패턴 따름
-
Import Style 적용
- Alias 사용 (설정된 경우)
- 상대 경로 스타일
-
Code Style 적용
- 기존 코드에서 학습한 패턴
- TypeScript/JavaScript 설정
Step 5: Display Result
═══════════════════════════════════════════════════════════════
SLICE CREATED: auth
═══════════════════════════════════════════════════════════════
📁 Created structure:
src/features/auth/
├── index.ts # Public API
├── ui/
│ ├── index.ts
│ ├── LoginForm.tsx
│ └── LoginForm.module.css
├── model/
│ ├── index.ts
│ ├── types.ts
│ └── useAuth.ts
├── api/
│ ├── index.ts
│ └── authApi.ts
└── lib/
└── index.ts
📝 Files created: 10
🎨 Pattern applied: kebab-case, barrel exports
💡 Next steps:
1. Implement your business logic in model/
2. Create UI components in ui/
3. Define API calls in api/
4. Export public interface through index.ts
═══════════════════════════════════════════════════════════════
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 · 295 lines · 10 tokens per session scan A 49c35f58c311
scaffold is a command published in the GitHub repository jhlee0409/claude-plugins (4 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 1,911 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".