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 skills/ww-w-ai/bkit-starter/setup-claude-codenpx skills add ww-w-ai/bkit-starter --skill setup-claude-codegit clone --depth 1 https://github.com/ww-w-ai/bkit-starterWrote 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/skills/ww-w-ai/bkit-starter/setup-claude-code)<a href="https://agentmods.dev/skills/ww-w-ai/bkit-starter/setup-claude-code"><img src="https://agentmods.dev/badge/skills/ww-w-ai/bkit-starter/setup-claude-code.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.00011 | $0.03074 |
| Opus 5 | $0.00005 | $0.01537 |
| Sonnet 5 | $0.00002 | $0.00615 |
| Haiku 4.5 | $0.00001 | $0.00307 |
Grade A, and why
setup-claude-code 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 5d 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code 프로젝트 설정 생성
어떤 프로젝트, 어떤 언어에서든 Claude Code 설정을 자동으로 생성합니다.
지원 언어: TypeScript, JavaScript, Python, Go, Rust, Java, C#, Ruby, PHP 등
사용법
/setup-claude-code [옵션]
옵션:
minimal: 최소 설정 (CLAUDE.md + 훅)standard: 표준 설정 (+ Commands, Agents)full: 전체 설정 (+ Skills, MCP, GitHub Action)- 생략 시: 프로젝트 분석 후 자동 결정
왜 이 커맨드가 필요한가?
문제: Claude Code 설정이 없거나 부족한 프로젝트에서 처음부터 수동 설정은 번거로움
해결: 프로젝트 분석 → 언어/구조에 맞는 초기 설정 자동 생성
결과: CLAUDE.md, .claude/, hooks, permissions 등 한 번에 설정
수행 작업
1단계: 마스터 가이드 참조
반드시 다음 문서를 먼저 읽습니다:
.claude/docs/CLAUDE-CODE-MASTERY.md # 목차 및 핵심 개념
.claude/docs/mastery/01-settings-guide.md # 설정 요소별 상세 가이드
.claude/docs/mastery/02-language-templates.md # 언어별 설정 템플릿
.claude/docs/mastery/03-project-structures.md # 프로젝트 구조별 가이드
필요한 내용에 따라 해당 파일을 참조합니다.
2단계: 프로젝트 분석
# 분석 대상
1. package.json → 패키지 매니저, 스크립트 확인
2. 폴더 구조 → 모노레포 여부, 모듈 구조
3. 기존 .claude/ → 이미 설정된 항목 확인
4. tsconfig.json → TypeScript 설정
5. .eslintrc / biome.json → 린트 설정
6. .prettierrc → 포맷터 설정
3단계: 기술 스택 파악
| 항목 | 확인 방법 |
|---|---|
| 패키지 매니저 | lockfile 확인 (pnpm-lock.yaml, package-lock.json, bun.lockb) |
| 언어 | tsconfig.json 유무, 파일 확장자 |
| 프레임워크 | package.json dependencies |
| 모노레포 | pnpm-workspace.yaml, turbo.json, lerna.json |
| 테스트 도구 | vitest, jest, mocha 등 |
4단계: 설정 규모 결정
## 규모 결정 기준
### Minimal (소규모, 1-3명)
- 단일 패키지
- 간단한 프로젝트
### Standard (중규모, 4-10명)
- 모노레포 또는 복잡한 단일 패키지
- 여러 개발자 협업
### Full (대규모, 10명+)
- 대규모 모노레포
- 여러 도메인
- 외부 시스템 연동 필요
5단계: 파일 생성
5.1 CLAUDE.md 생성 (항상)
# Development Workflow
## 패키지 관리
- **항상 `{detected_package_manager}` 사용**
## 개발 순서
1. 변경 사항 작성
2. 타입체크: `{typecheck_command}`
3. 테스트: `{test_command}`
4. 린트: `{lint_command}`
5. 빌드: `{build_command}`
## 코딩 컨벤션
- `type` 선호, `interface` 자제
- **`enum` 절대 금지** → 문자열 리터럴 유니온 사용
- Zod 스키마로 타입 정의
## 프로젝트 구조
{detected_structure}
## 금지 사항
- ❌ console.log 대신 logger 사용
- ❌ any 타입 사용 금지
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.
- 5d ago First seen · 439 lines · 11 tokens per session scan A 888319ee09ad
setup-claude-code is a skill published in the GitHub repository ww-w-ai/bkit-starter (53 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 3,074 once invoked, about $0.0001 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…