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/cyvid7-darus10/claude-code-config/tddgit clone --depth 1 https://github.com/Cyvid7-Darus10/claude-code-configWrote 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/cyvid7-darus10/claude-code-config/tdd)<a href="https://agentmods.dev/commands/cyvid7-darus10/claude-code-config/tdd"><img src="https://agentmods.dev/badge/commands/cyvid7-darus10/claude-code-config/tdd.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.00028 | $0.02223 |
| Opus 5 | $0.00014 | $0.01111 |
| Sonnet 5 | $0.00006 | $0.00445 |
| Haiku 4.5 | $0.00003 | $0.00222 |
Grade A, and why
tdd 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.
This is a copy
77% identical to tdd — 202 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Command
This command invokes the tdd-guide agent to enforce test-driven development methodology.
What This Command Does
- Scaffold Interfaces - Define types/interfaces first
- Generate Tests First - Write failing tests (RED)
- Implement Minimal Code - Write just enough to pass (GREEN)
- Refactor - Improve code while keeping tests green (REFACTOR)
- Verify Coverage - Ensure 80%+ test coverage
When to Use
Use /tdd when:
- Implementing new features
- Adding new functions/components
- Fixing bugs (write test that reproduces bug first)
- Refactoring existing code
- Building critical business logic
How It Works
The tdd-guide agent will:
- Define interfaces for inputs/outputs
- Write tests that will FAIL (because code doesn't exist yet)
- Run tests and verify they fail for the right reason
- Write minimal implementation to make tests pass
- Run tests and verify they pass
- Refactor code while keeping tests green
- Check coverage and add more tests if below 80%
TDD Cycle
RED → GREEN → REFACTOR → REPEAT
RED: Write a failing test
GREEN: Write minimal code to pass
REFACTOR: Improve code, keep tests passing
REPEAT: Next feature/scenario
Example Usage
User: /tdd I need a function to calculate market liquidity score
Agent (tdd-guide):
# TDD Session: Market Liquidity Score Calculator
## Step 1: Define Interface (SCAFFOLD)
```typescript
// lib/liquidity.ts
export interface MarketData {
totalVolume: number
bidAskSpread: number
activeTraders: number
lastTradeTime: Date
}
export function calculateLiquidityScore(market: MarketData): number {
// TODO: Implementation
throw new Error('Not implemented')
}
Step 2: Write Failing Test (RED)
// lib/liquidity.test.ts
import { calculateLiquidityScore } from './liquidity'
describe('calculateLiquidityScore', () => {
it('should return high score for liquid market', () => {
const market = {
totalVolume: 100000,
bidAskSpread: 0.01,
activeTraders: 500,
lastTradeTime: new Date()
}
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 · 329 lines · 28 tokens per session scan A 9f054ac6db11
tdd is a command published in the GitHub repository Cyvid7-Darus10/claude-code-config (2 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 2,223 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 77% identical to tdd, differing in 202 lines, and is treated as a copy.
Other commands, from other repositories
speckit.model-selector
Select the best OpenRouter model for each SpecKit workflow step and write model metadata into each command file.
prepare-dataset
Analyse a raw data file (CSV, JSON, JSONL, TSV, Parquet) and generate a complete Python script scripts/dataset/ .py that inherits from BaseDatasetPreparer and transforms the file into a JSONL dataset ready for fine-tuning with Unsloth.
speckit.polish
Polish and complete speckit workflow — quality gate, docs, changelog, MR.
documentation
Strictly follow the project constitution.
publish
Release a new package version — semver bump from commits, tag, registry publish, GitHub Release.
next-sprint-design
You are helping a DevOps engineer prepare a sprint kickoff message for Slack.