A project configuration command sets the rules for pairing source files with their tests in strict test-driven development (TDD).

It configures test-file naming patterns, exemptions, and whether source and test files may be added in the same commit.

It defines how the commit check finds tests and which files or directories are exempt, reducing uncertainty about test-first requirements.

tdd-config — Command for Claude Code by studioKjm

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/studioKjm/ai-harness-template

agentmods

npx agentmods add commands/studiokjm/ai-harness-template/tdd-config

Made for: Claude Code.

Or install harness, the plugin that ships this one along with the rest of its 44 commands, 11 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/studiokjm/ai-harness-template/tdd-config/github.svg)](https://agentmods.dev/commands/studiokjm/ai-harness-template/tdd-config)

Your own site

<a href="https://agentmods.dev/commands/studiokjm/ai-harness-template/tdd-config"><img src="https://agentmods.dev/badge/commands/studiokjm/ai-harness-template/tdd-config/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/studiokjm/ai-harness-template/tdd-config"><img src="https://agentmods.dev/badge/commands/studiokjm/ai-harness-template/tdd-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 423 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00423
Opus 5	$0.00000	$0.00211
Sonnet 5	$0.00000	$0.00085
Haiku 4.5	$0.00000	$0.00042

Measured 9d ago against content hash 6d278be64be1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

tdd-config 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 9d 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.

methodologies/tdd-strict/commands/tdd-config.md · 88 lines

What it actually says

/tdd-config — TDD Configuration

Methodology: tdd-strict
Purpose: Configure test pairing conventions and gate behavior for this project.

Setup

Copy the template and customize:

mkdir -p .harness/tdd-strict
cp methodologies/tdd-strict/templates/tdd-config.yaml .harness/tdd-strict/config.yaml

Key Settings

Test Pairing Conventions

Tell the gate how to find the test file for a given source file:

pairing:
  conventions:
    - source: "src/**/*.ts"
      test: "src/**/*.test.ts"
    - source: "src/**/*.ts"
      test: "src/**/*.spec.ts"

The gate resolves pairs at commit time using git log to verify history order.

Exempt Directories

pairing:
  exempt_dirs:
    - "migrations/"
    - "scripts/"
    - "config/"

Source files in these directories skip the test-first check entirely.

Exempt Patterns

pairing:
  exempt_patterns:
    - "index.ts"      # Re-export barrels
    - "types.ts"      # Pure type definitions
    - "constants.ts"  # Constants only

Allow Same-Commit

gate:
  allow_same_commit: false   # true: test and source may appear in same commit

Default is false (test must appear in an earlier commit). Set to true for teams that prefer atomic test+source commits.

Gate Severity

gate:
  severity: "blocking"   # or "warning"

Switch to warning during ramp-up to measure violations without blocking.

Verifying Configuration

# Run gate manually
HARNESS_DIR=.harness bash methodologies/tdd-strict/gates/check-test-first.sh

# Check cycle list
python3 methodologies/tdd-strict/scripts/tdd.py list

Changes

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.

9d ago First seen · 88 lines · 0 tokens per session scan A 6d278be64be1

Subscribe to this mod's changes

tdd-config 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 423 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.

Claude Code Guardrails TDD Testing ai-agent ai-harness developer-tools harness-engineering

tdd-config