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/crudnpx skills add demodev-lab/claude-code-plugin-demokit --skill crudgit clone --depth 1 https://github.com/demodev-lab/claude-code-plugin-demokitWrote 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/demodev-lab/claude-code-plugin-demokit/crud)<a href="https://agentmods.dev/skills/demodev-lab/claude-code-plugin-demokit/crud"><img src="https://agentmods.dev/badge/skills/demodev-lab/claude-code-plugin-demokit/crud.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.00052 | $0.01558 |
| Opus 5 | $0.00026 | $0.00779 |
| Sonnet 5 | $0.00010 | $0.00312 |
| Haiku 4.5 | $0.00005 | $0.00156 |
Grade A, and why
crud 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 4d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/crud - 도메인 CRUD 일괄 생성
Spring Boot 3.5.10 + Java 21 모던 패턴 적용
help
인자가 help이면 아래 도움말만 출력하고 실행을 중단한다:
/crud — 도메인 CRUD 일괄 생성 (Entity, Repository, Service, Controller, DTO)
사용법:
/crud {Name} [fields]
파라미터:
Name PascalCase 도메인명 (필수)
fields 필드 목록 (선택, 형식: name:String, email:String)
예시:
/crud User
/crud User name:String, email:String, age:Integer
/crud Order orderNumber:String, totalAmount:BigDecimal
관련 명령:
/entity — JPA Entity 생성
/test — 테스트 코드 생성
/pdca plan — PDCA 워크플로우 시작
실행 절차
1. 입력 검증
- domainName이 PascalCase인지 확인
- 프로젝트 base package가 감지되었는지 확인
- 이미 존재하는 도메인인지 확인
2. 필드 분석
컨벤션:
templates/shared/ask-user-convention.md참조
- fields가 제공된 경우 파싱
- fields가 없으면
AskUserQuestion도구로 추가 옵션을 질문한다:- Q1 (header: "QueryDSL"): QueryDSL 동적 쿼리 포함 여부
기본 CRUD만 (Recommended)— JpaRepository 기본 메서드만 생성QueryDSL 포함— 동적 검색/필터링 Custom Repository 함께 생성
- Q2 (header: "Soft Delete"): 삭제 전략
Hard Delete (Recommended)— 실제 삭제Soft Delete— deleted 플래그 사용, @SQLRestriction 적용
- Q1 (header: "QueryDSL"): QueryDSL 동적 쿼리 포함 여부
- 필드별 타입 → JPA 컬럼 타입 매핑
3. 파일 생성 (병렬 전략)
Phase 1 — 기반 생성 (순차) BaseEntity, GlobalExceptionHandler가 없으면 먼저 생성한다.
Phase 2 — 독립 레이어 병렬 생성 다음 작업을 Task 도구로 한 메시지에서 동시에 호출한다:
| Task # | 담당 | 생성 파일 |
|---|---|---|
| Task 1 | domain-expert | Entity (domain/{domainName}/entity/{DomainName}.java), Repository (domain/{domainName}/repository/{DomainName}Repository.java) |
| Task 2 | api-expert | CreateRequest DTO (domain/{domainName}/dto/Create{DomainName}Request.java), UpdateRequest DTO (domain/{domainName}/dto/Update{DomainName}Request.java), Response DTO (domain/{domainName}/dto/{DomainName}Response.java) |
| Task 3 | (선택) QueryDSL | CustomRepository, Impl, SearchCondition, QuerydslConfig |
각 파일의 상세 규칙:
- Entity: BaseEntity 상속, @Entity, @Getter, @NoArgsConstructor(access = PROTECTED), @Builder private 생성자
- Repository: JpaRepository 상속, default 메서드
getById()패턴 - Request DTO: 반드시 Java
record, Bean Validation 어노테이션 직접 선언 - Response DTO: 반드시 Java
record,from()정적 메서드
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.
- 4d ago First seen · 148 lines · 52 tokens per session scan A a9e1ce7d6c13
crud is a skill published in the GitHub repository demodev-lab/claude-code-plugin-demokit (2 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 1,558 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…