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 skills add JeonJe/claude-plugins --skill spring-ddd-archgit clone --depth 1 https://github.com/JeonJe/claude-pluginsWrote 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/jeonje/claude-plugins/spring-ddd-arch)<a href="https://agentmods.dev/skills/jeonje/claude-plugins/spring-ddd-arch"><img src="https://agentmods.dev/badge/skills/jeonje/claude-plugins/spring-ddd-arch.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.1 | $0.00105 | $0.00956 |
| Opus 5 | $0.00053 | $0.00478 |
| Sonnet 5 | $0.00021 | $0.00191 |
| Haiku 4.5 | $0.00011 | $0.00096 |
Grade A, and why
spring-ddd-arch 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 7d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring DDD Architecture
운영 서비스에서 다듬어진 Java/Spring 백엔드 아키텍처 규칙. 핵심은 경계 — 계층 간 호출 방향, 도메인과 인프라의 분리(DIP), 발행 책임의 위치를 고정해서 기능이 늘어나도 구조가 무너지지 않게 한다.
계층 구조
Controller → Facade → Service → Repository → Domain
| 계층 | 책임 |
|---|---|
| Controller | 요청 수신, validation, 응답 반환 |
| Facade | 여러 Service 조합, 트랜잭션 경계 |
| Service | 단일 도메인 비즈니스 로직 |
| Repository | 데이터 접근 (JPA/QueryDSL/MyBatis) |
| Domain | 엔티티, VO, 도메인 이벤트 |
위반 금지:
- Controller → Repository 직접 호출
- Service → Service 순환 참조
- Facade = 흐름 제어만. 캐시/Redis 등 인프라 사용 여부를 몰라야 한다 — 인프라는 포트/Reader 인터페이스 뒤로 (DIP). 발행 경로를 optional 빈(
ObjectProvider)·조건부로 분기하지 않는다. - 비즈니스 로직은 Service 또는 Domain 레이어에만.
예외 설계 — 기본 예외 직접 throw 금지
new IllegalArgumentException, new RuntimeException 등 Java 기본 예외를 직접 throw하지 않는다. 프로젝트 커스텀 예외 + 에러 레벨을 사용해, 예외 하나가 로깅·모니터링·알림 정책까지 결정하게 한다. 상세: references/exception-design.md
도메인 이벤트 — 기록(raise) ≠ 발송(dispatch)
상태를 바꾸는 도메인이 자신의 이벤트를 책임진다. Facade에서 발행하지 않는다. 엔티티에 ApplicationEventPublisher를 주입하지 않는다. 상세: references/domain-events.md
References index
| File | Read when |
|---|---|
| references/domain-events.md | 도메인 이벤트 발행/구독을 설계·리뷰할 때 |
| references/exception-design.md | 예외 클래스/에러 응답을 만들 때 |
| references/domain-model-patterns.md | 엔티티/VO 설계 — soft delete, audit, 민감정보 암호화, First-Class Collection |
| references/performance.md | JPA/QueryDSL 조회, 직렬화, 캐시, 비동기 코드를 쓸 때 |
| references/transactions.md | 트랜잭션 경계/선언, 부수효과, 다중 DataSource, 테스트에서의 함정 |
| references/concurrency.md | 동시성 제어 — 자원/행위자 이중 직렬화, 락 순서, 메커니즘 선택의 근거 |
| references/sql-domain-boundary.md | 집계/통계 쿼리 — SQL과 도메인의 책임 분리, 반열림 구간·제로패딩 등 함정 목록 |
| references/api-contract.md | API 표면 설계 — 상태코드, 에러 포맷, 컬렉션 규약, 하위호환 변경 절차 |
| references/db-migration.md | 스키마 변경 — expand-contract, NOT NULL 절차, 대용량 테이블, 롤백 계획 |
| references/time-handling.md | 시간 — 저장 기준 단일화, 타입 선택, Clock 주입, 경계 케이스 박제 |
What ships with it
10 files 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.
- references/api-contract.md 2.6 KB
- references/concurrency.md 3.4 KB
- references/db-migration.md 2.3 KB
- references/domain-events.md 2.0 KB
- references/domain-model-patterns.md 2.8 KB
- references/exception-design.md 3.1 KB
- references/performance.md 2.1 KB
- references/sql-domain-boundary.md 3.5 KB
- references/time-handling.md 2.0 KB
- references/transactions.md 4.6 KB
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.
- 7d ago First seen · 52 lines · 105 tokens per session scan A a1c25ddf341f
spring-ddd-arch is a skill published in the GitHub repository JeonJe/claude-plugins (3 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 956 once invoked, about $0.0005 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
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
dependency-injection
Use when writing or reviewing code with object graphs, service dependencies, or testability concerns. Covers constructor injection, DI containers, lifetimes, and anti-patterns (service locator, ambient context, over-injection).
.NET Patterns
Use this skill when working in .NET projects (C#) and you want clean layering, safe async usage, and maintainable dependency injection patterns.
testing
Testing patterns with Vitest and Playwright for NestJS backend services. Use when writing unit tests, integration tests, or E2E tests for controllers, services, guards, and pipes.
typescript-sdk
Implement or modify TypeScript SDK behavior in @composio/core or shared TypeScript packages, including tools, toolkits, sessions, auth configs, connected accounts, modifiers, and generated SDK surfaces. Use for TS runtime/API work; pair with typescript-testing for verification and cross-sdk-parity when Python must…
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.