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/helpnpx skills add demodev-lab/claude-code-plugin-demokit --skill helpgit 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.00053 | $0.00690 |
| Opus 5 | $0.00026 | $0.00345 |
| Sonnet 5 | $0.00011 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
help 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 2d 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.
What it actually says
/help - 전체 커맨드 목록
아래 도움말을 출력하고 실행을 중단한다:
사용 가능한 커맨드
━━━━━━━━━━━━━━━━━━━━
프로젝트
/init — Spring Boot 프로젝트 감지 및 초기화
도메인 CRUD
/crud — 도메인 CRUD 일괄 생성 (Entity, Repository, Service, Controller, DTO)
/entity — JPA Entity 생성
/repository — Spring Data JPA Repository 생성
/service — Service 레이어 생성
/controller — REST Controller 생성
/dto — Java record 기반 Request/Response DTO 생성
설정·인프라
/exception — 도메인 예외 및 GlobalExceptionHandler 생성
/config — Spring 설정 클래스 생성
/security — Spring Security 설정 생성 (JWT/OAuth2)
/cache — 캐싱 전략 설정 (Caffeine/Redis)
/gradle — Gradle 의존성 관리
/docker — Docker/Docker Compose 설정 생성
/api-docs — SpringDoc/Swagger API 문서화 설정 생성
/migration — DB 마이그레이션 파일 생성
분석·도구
/erd — Mermaid ERD 다이어그램 생성
/changelog — Git 기반 CHANGELOG 자동 생성
/properties — Spring Boot 설정 관리 (프로파일 분리, 검증)
테스트
/test — 단위/통합/슬라이스 테스트 코드 생성
워크플로우
/pdca — PDCA 워크플로우 (plan/design/do/analyze/iterate/report/archive/cleanup)
/pipeline — Spring Boot 9단계 개발 파이프라인
/plan-plus — 5단계 브레인스토밍 강화 계획 (--deep 지원)
/loop — 작업 완료까지 자동 반복 실행
/cancel-loop — 활성화된 자율 반복 루프 취소
품질/분석
/review — 정적 코드 분석 (아키텍처/패턴/보안) [--deep]
/review full — 통합 품질 파이프라인 (리뷰+최적화+QA) [--fix] [--deep]
/optimize — 성능 최적화 분석 (N+1/인덱스/트랜잭션) [--fix]
/qa — 동적 품질 검증 (빌드/테스트/로그) [build|test|log|summary]
Git
/commit — 변경사항을 논리적 단위로 스마트 커밋
/commit-push — 커밋 후 원격 저장소에 푸시
/push — 현재 브랜치를 원격 저장소에 푸시
/pr — Pull Request 생성
자세한 사용법: /{name} help
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.
- 2d ago First seen · 64 lines · 53 tokens per session scan A 19022c793b5f
help is a skill published in the GitHub repository demodev-lab/claude-code-plugin-demokit (2 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 690 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.
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…