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.
git clone --depth 1 https://github.com/studioKjm/ai-harness-templateWrote 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/commands/studiokjm/ai-harness-template/ddd-glossary)<a href="https://agentmods.dev/commands/studiokjm/ai-harness-template/ddd-glossary"><img src="https://agentmods.dev/badge/commands/studiokjm/ai-harness-template/ddd-glossary/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/studiokjm/ai-harness-template/ddd-glossary"><img src="https://agentmods.dev/badge/commands/studiokjm/ai-harness-template/ddd-glossary.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00353 |
| Opus 5 | $0.00000 | $0.00177 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
ddd-glossary 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 10d 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
/ddd-glossary — Ubiquitous Language Glossary
팀 전체가 공유하는 도메인 용어집을 관리합니다. 코드의 클래스/함수명과 대화의 언어가 일치하도록 강제합니다.
Usage
/ddd-glossary add <term> [--context|-c <BC-ID>] [--definition|-d <def>]
/ddd-glossary list [--context|-c <BC-ID>]
/ddd-glossary show <term>
왜 Ubiquitous Language가 중요한가
❌ 나쁜 예:
- 기획서: "고객이 장바구니에 담는다"
- DB 테이블: cart_items
- 코드 클래스: ShoppingBasket
- API: POST /orders/pending
→ 4가지 언어가 모두 다름 — 대화할 때마다 번역 비용 발생
✅ 좋은 예:
- 기획서: "고객이 장바구니에 담는다"
- DB 테이블: cart_items
- 코드 클래스: Cart
- API: POST /cart/items
- 용어집: Cart = "고객이 주문 전 상품을 임시 보관하는 컨테이너"
Tips
disputed상태: 팀 내 용어 합의가 안 된 경우 표시 → 정기 용어 리뷰 세션 필요cross_context: 같은 개념이 다른 컨텍스트에서 다른 이름일 때 명시 (예: Order ↔ Purchase)synonyms: 쓰면 안 되는 대체 표현 목록 (코드 리뷰에서 잡을 수 있도록)
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.
- 10d ago First seen · 37 lines · 0 tokens per session scan A 955c30f7c93c
ddd-glossary is a command published in the GitHub repository studioKjm/ai-harness-template (43 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 353 tokens. 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 commands, from other repositories
capture-feedback
Quick feedback capture with structured signals.
show-lessons
Display promoted lessons and their corrective actions.
harness-review
Review the current change set from an opposing harness-engineering perspective.
step0-specify-feature
Pipeline Step 0 — Specify what you want to build and why, before any technical planning. Surfaces ambiguities early with [NEEDS CLARIFICATION] markers.
harness-update
Update a target repository's harness from the latest harness-starter-kit reference material.
harness-doctor
Run Harness Doctor to evaluate how ready the current repository is for reliable AI coding agent collaboration.