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/demodev-lab/claude-code-plugin-demokit/commitnpx skills add demodev-lab/claude-code-plugin-demokit --skill commitgit clone --depth 1 https://github.com/demodev-lab/claude-code-plugin-demokitWhat 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.00051 | $0.00949 |
| Opus 5 | $0.00026 | $0.00475 |
| Sonnet 5 | $0.00010 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
commit 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 yesterday.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/commit - 스마트 커밋
help
인자가 help이면 아래 도움말만 출력하고 실행을 중단한다:
/commit — 변경사항을 논리적 단위로 스마트 커밋
사용법:
/commit [message]
파라미터:
message 커밋 메시지 (선택, 없으면 논리적 그룹 분류)
예시:
/commit
/commit "feat: User 엔티티 추가"
관련 명령:
/commit-push — 커밋 후 원격 푸시
/push — 원격 푸시
실행 절차
1. 변경사항 분석
아래 3개 명령을 병렬로 실행하여 현재 상태를 파악한다:
git status
git diff
git diff --cached
변경사항이 없으면 "커밋할 변경사항이 없습니다." 출력 후 종료.
2. 커밋 방식 결정
message 인자가 있는 경우:
- 모든 변경 파일을 하나로 묶어 커밋 → Step 5로 이동
message 인자가 없는 경우:
- 변경 파일들을 논리적 그룹으로 분류 → Step 3으로 이동
3. 논리적 그룹 분류
변경된 파일들을 아래 기준으로 그룹화:
| 우선순위 | 기준 | 예시 |
|---|---|---|
| 1 | 동일 도메인 디렉토리 (domain/{name}/) |
domain/user/User.java + domain/user/UserRepository.java |
| 2 | 설정 파일 (application.yml, build.gradle, config 등) |
application.yml, build.gradle.kts |
| 3 | 공통 모듈 (common/, global/, shared/) |
common/exception/ErrorCode.java |
| 4 | 인프라 (infra/, config/) |
infra/redis/RedisConfig.java |
| 5 | 문서 (.md 파일) |
README.md, CHANGELOG.md |
| 6 | 기타 | 위에 해당하지 않는 파일 |
규칙:
- 테스트 파일은 해당 구현 파일과 같은 그룹에 포함
- 하나의 파일이 여러 그룹에 해당하면 가장 구체적인 그룹에 배치
4. 사용자 확인
컨벤션:
templates/shared/ask-user-convention.md참조
그룹별 커밋 계획을 표로 먼저 출력한 뒤, AskUserQuestion 도구로 확인받는다:
| # | 커밋 메시지 | 파일 |
|---|-----------|------|
| 1 | feat: User 엔티티 및 Repository 추가 | domain/user/User.java, domain/user/UserRepository.java |
| 2 | chore: Redis 의존성 추가 | build.gradle.kts |
- question: "위 커밋 계획대로 진행할까요?"
- header: "커밋 확인"
- options:
진행 (Recommended)— 위 계획대로 커밋 실행수정 필요— 그룹 분류나 메시지 변경 요청
5. 커밋 실행
그룹별로 순차 실행:
git add <파일1> <파일2> ...
git commit -m "<type>: <subject>"
6. 결과 출력
✓ 커밋 완료 (N개)
abc1234 feat: User 엔티티 및 Repository 추가
def5678 chore: Redis 의존성 추가
커밋 메시지 규칙
- 형식:
<type>: <subject> - type:
feat,fix,refactor,chore,docs,test,style - subject: 한국어, 명령형
- 이모지 사용 금지
Co-Authored-By,Generated with Claude Code, AI 관련 문구 절대 포함 금지- HEREDOC 형식 사용:
git commit -m "$(cat <<'EOF'
<type>: <subject>
EOF
)"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 113 lines · 51 tokens per session scan A 197093b4bb83
commit is a skill published in the GitHub repository demodev-lab/claude-code-plugin-demokit (2 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 949 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…