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 commands/studiokjm/ai-harness-template/bddgit 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/bdd)<a href="https://agentmods.dev/commands/studiokjm/ai-harness-template/bdd"><img src="https://agentmods.dev/badge/commands/studiokjm/ai-harness-template/bdd.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.00000 | $0.00650 |
| Opus 5 | $0.00000 | $0.00325 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
bdd 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 5d 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
/bdd — BDD Scenario Command
Given/When/Then 시나리오를 작성하고 구현 상태를 추적합니다.
Usage
/bdd new <title> [--feature|-f <FTR-ID>]
/bdd list [--state|-s <state>] [--feature|-f <FTR-ID>]
/bdd show <SCN-ID>
/bdd status <SCN-ID> <state>
/bdd link <SCN-ID> [--tdd <TDD-ID>] [--story <story-id>] [--rfc <RFC-ID>]
States
draft → ready → implementing → passing
↘ skipped
| State | 의미 |
|---|---|
draft |
시나리오 작성 중 |
ready |
Given/When/Then 완성, 구현 준비 |
implementing |
TDD 사이클과 연결, 구현 중 |
passing |
테스트 통과 확인 |
skipped |
범위 외 또는 향후 구현 예정 |
Workflow
1. /bdd new "고객이 상품을 장바구니에 추가할 수 있다"
2. # .harness/bdd/scenarios/SCN-20260501-001-고객이-상품을.yaml 편집
3. /bdd status SCN-001 ready
4. /bdd link SCN-001 --tdd TDD-20260501-001 # TDD 사이클 연결
5. /bdd status SCN-001 implementing
6. # 구현 완료 후
7. /bdd status SCN-001 passing
BDD 3 Amigos
시나리오 작성 전 세 가지 관점 확인:
- Product (기획): "어떤 문제를 해결하나?"
- Dev (개발): "어떻게 구현하나?"
- QA (테스트): "어떻게 검증하나?"
Given/When/Then 작성 규칙
# ✅ 좋은 예 — 구체적이고 단일 행동
given:
- "고객 계정이 존재한다"
- "장바구니가 비어있다"
when:
- "고객이 상품 ID 'PROD-001'을 장바구니에 추가한다"
then:
- "장바구니에 상품이 1개 있다"
- "장바구니 총액이 10,000원이다"
# ❌ 나쁜 예 — 너무 광범위
given:
- "시스템이 준비되어 있다"
when:
- "사용자가 모든 것을 한다"
then:
- "잘 된다"
Composition
/methodology compose bdd tdd-strict # 시나리오 → TDD 사이클로 세분화
/methodology compose bdd ddd-lite # Feature = Bounded Context 단위
/methodology compose bdd living-spec # 시나리오가 살아있는 명세의 일부
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.
- 5d ago First seen · 78 lines · 0 tokens per session scan A 8cc65fa07643
bdd 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 650 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
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.
VibeGuard: Live Truth
Verify live claims with fresh facts, inferences, and unresolved gaps.
capture-feedback
Quick feedback capture with structured signals.
check-gates
Run a Pre-Action Gate check against prevention rules before executing a risky action.
harness-adopt
Apply Harness Starter Kit to the current target repository with the prompt-first adoption workflow.