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/cfrs2005/claude-init/tddgit clone --depth 1 https://github.com/cfrs2005/claude-initWhat 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.00037 | $0.02640 |
| Opus 5 | $0.00018 | $0.01320 |
| Sonnet 5 | $0.00007 | $0.00528 |
| Haiku 4.5 | $0.00004 | $0.00264 |
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 yesterday.
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.
Copies of this mod
8 near-identical copies found in the catalogue:
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 指令 (TDD Command)
此指令调用 TDD 向导 (tdd-guide) 智能体,以强制执行测试驱动开发 (TDD) 方法论。
此指令的功能
- 搭建接口 - 首先定义类型/接口
- 先写测试 - 编写会失败的测试 (红)
- 实现最小代码 - 编写刚好能通过测试的代码 (绿)
- 重构 - 在保持测试通过的前提下改进代码 (重构)
- 验证覆盖率 - 确保 80% 以上的测试覆盖率
何时使用
在以下情况使用 /tdd:
- 实现新功能时
- 添加新函数/组件时
- 修复 Bug 时 (先写一个能复现 Bug 的测试)
- 重构现有代码时
- 构建关键业务逻辑时
工作原理
TDD 向导智能体将:
- 定义接口 用于输入/输出
- 编写会失败的测试 (因为代码还不存在)
- 运行测试 并验证它们因正确的原因而失败
- 编写最小实现 以通过测试
- 运行测试 并验证它们通过
- 重构 代码,同时保持测试通过
- 检查覆盖率 如果低于 80%,则添加更多测试
TDD 循环
红 (RED) → 绿 (GREEN) → 重构 (REFACTOR) → 重复 (REPEAT)
红 (RED): 编写一个失败的测试
绿 (GREEN): 编写最小代码以通过测试
重构 (REFACTOR): 改进代码,保持测试通过
重复 (REPEAT): 处理下一个功能/场景
使用示例
User: /tdd I need a function to calculate market liquidity score
(用户:/tdd 我需要一个计算市场流动性得分的函数)
Agent (tdd-guide):
# TDD Session: Market Liquidity Score Calculator
(TDD 会话:市场流动性得分计算器)
## Step 1: Define Interface (SCAFFOLD) (步骤 1:定义接口)
```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) (步骤 2:编写失败测试 - 红)
// 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()
}
const score = calculateLiquidityScore(market)
expect(score).toBeGreaterThan(80)
expect(score).toBeLessThanOrEqual(100)
})
it('should return low score for illiquid market', () => {
const market = {
totalVolume: 100,
bidAskSpread: 0.5,
activeTraders: 2,
lastTradeTime: new Date(Date.now() - 86400000) // 1 day ago
}
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.
- yesterday First seen · 329 lines · 37 tokens per session scan A 13540a980560
tdd is a command published in the GitHub repository cfrs2005/claude-init (1,365 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 2,640 once invoked, about $0.0002 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.