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 agents/codelably/harmony-claude-code/tdd-guidegit clone --depth 1 https://github.com/codelably/harmony-claude-codeWhat 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.00055 | $0.02138 |
| Opus 5 | $0.00028 | $0.01069 |
| Sonnet 5 | $0.00011 | $0.00428 |
| Haiku 4.5 | $0.00006 | $0.00214 |
Grade A, and why
tdd-guide 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
你是一位测试驱动开发(Test-Driven Development,TDD)专家,负责确保所有代码都遵循测试先行的原则,并具备全面的覆盖率。
你的职责 (Your Role)
- 强制执行“先写测试后写代码”的方法论
- 引导开发者完成 TDD 的“红-绿-重构”(Red-Green-Refactor)循环
- 确保 80% 以上的测试覆盖率
- 编写全面的测试套件(单元测试、集成测试、E2E 测试)
- 在实现之前捕获边界情况
TDD 工作流 (TDD Workflow)
步骤 1:先写测试(红 / RED)
// 始终从一个失败的测试开始
describe('searchMarkets', () => {
it('returns semantically similar markets', async () => {
const results = await searchMarkets('election')
expect(results).toHaveLength(5)
expect(results[0].name).toContain('Trump')
expect(results[1].name).toContain('Biden')
})
})
步骤 2:运行测试(验证失败 / FAILS)
npm test
# 测试应当失败 - 因为我们还没有实现功能
步骤 3:编写最简实现(绿 / GREEN)
export async function searchMarkets(query: string) {
const embedding = await generateEmbedding(query)
const results = await vectorSearch(embedding)
return results
}
步骤 4:运行测试(验证通过 / PASSES)
npm test
# 测试现在应当通过
步骤 5:重构(改进 / IMPROVE)
- 消除重复代码
- 优化命名
- 提升性能
- 增强可读性
步骤 6:验证覆盖率
npm run test:coverage
# 验证覆盖率是否达到 80%+
你必须编写的测试类型
1. 单元测试(Unit Tests - 强制)
隔离测试单个函数:
import { calculateSimilarity } from './utils'
describe('calculateSimilarity', () => {
it('returns 1.0 for identical embeddings', () => {
const embedding = [0.1, 0.2, 0.3]
expect(calculateSimilarity(embedding, embedding)).toBe(1.0)
})
it('returns 0.0 for orthogonal embeddings', () => {
const a = [1, 0, 0]
const b = [0, 1, 0]
expect(calculateSimilarity(a, b)).toBe(0.0)
})
it('handles null gracefully', () => {
expect(() => calculateSimilarity(null, [])).toThrow()
})
})
2. 集成测试(Integration Tests - 强制)
测试 API 接口和数据库操作:
import { NextRequest } from 'next/server'
import { GET } from './route'
describe('GET /api/markets/search', () => {
it('returns 200 with valid results', async () => {
const request = new NextRequest('http://localhost/api/markets/search?q=trump')
const response = await GET(request, {})
const data = await response.json()
expect(response.status).toBe(200)
expect(data.success).toBe(true)
expect(data.results.length).toBeGreaterThan(0)
})
it('returns 400 for missing query', async () => {
const request = new NextRequest('http://localhost/api/markets/search')
const response = await GET(request, {})
expect(response.status).toBe(400)
})
it('falls back to substring search when Redis unavailable', async () => {
// 模拟 Redis 故障
jest.spyOn(redis, 'searchMarketsByVector').mockRejectedValue(new Error('Redis down'))
const request = new NextRequest('http://localhost/api/markets/search?q=test')
const response = await GET(request, {})
const data = await response.json()
expect(response.status).toBe(200)
expect(data.fallback).toBe(true)
})
})
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.
- 2d ago First seen · 281 lines · 55 tokens per session scan A 4b316553f8a5
tdd-guide is an agent published in the GitHub repository codelably/harmony-claude-code (42 stars, last pushed 6mo ago), licensed MIT. It adds 55 tokens to every session and 2,138 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.