Borrowing it
Nothing to install: this file belongs to znlnzi/claude-config-studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/znlnzi/claude-config-studio/main/.claude/skills/tdd-workflow/SKILL.mdgit clone --depth 1 https://github.com/znlnzi/claude-config-studioWrote 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/skills/znlnzi/claude-config-studio/tdd-workflow)<a href="https://agentmods.dev/skills/znlnzi/claude-config-studio/tdd-workflow"><img src="https://agentmods.dev/badge/skills/znlnzi/claude-config-studio/tdd-workflow/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.
<a href="https://agentmods.dev/skills/znlnzi/claude-config-studio/tdd-workflow"><img src="https://agentmods.dev/badge/skills/znlnzi/claude-config-studio/tdd-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00358 |
| Opus 5 | $0.00012 | $0.00179 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
tdd-workflow 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 8d 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
TDD 工作流技能
核心流程
- 用户旅程 - 将需求记录为 "作为[角色]，我想要..."
- 编写测试 - 在实现前创建全面的测试用例
- 运行测试（失败） - 确认测试在没有代码的情况下失败
- 实现代码 - 编写满足测试的最小代码
- 运行测试（通过） - 验证所有测试成功
- 重构 - 在保持绿色测试的同时提高代码质量
- 验证覆盖率 - 确保达到 80%+ 阈值
测试类别
单元测试
- Jest/Vitest 用于函数、组件、工具
- 模拟外部依赖
- 执行快速（< 50ms）
集成测试
- API 端点测试
- 数据库操作测试
- 服务交互测试
E2E 测试
- Playwright 测试关键用户流程
- 使用语义选择器
- 独立可重复
覆盖率标准
- 最低 80%（单元 + 集成 + E2E）
- 关键路径 100%（认证、支付、安全）
- 覆盖边缘情况和错误场景
成功指标
- 80%+ 代码覆盖率
- 所有测试一致通过
- 快速执行（单元测试 < 50ms）
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.
- 8d ago First seen · 46 lines · 23 tokens per session scan A 562cafc7ee0d
tdd-workflow is a skill published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 358 once invoked, about $0.0001 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-31.
Other skills, from other repositories
jest-patterns
Jest and Vitest testing patterns including describe/it blocks, expect matchers, mocking, and async test strategies for JavaScript and TypeScript.
mocking-strategies
Mock, patch, fake, and stub patterns for isolating dependencies in Python and JavaScript test suites.
pytest-patterns
Pytest best practices including fixtures, parametrize, markers, and assertion patterns for Python test suites.
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
fix-bug
Investigates and fixes a reported bug. Reads relevant code, identifies the root cause, proposes a fix, and adds or updates tests to prevent regression. Invoked when the user describes unexpected behavior, an error, a crash, or a failing test.
add-tests
Generates tests for existing code. Analyzes the target function, method, or class to identify the happy path, error cases, and edge cases, then writes test cases following the project's testing framework and naming conventions. Invoked when the user asks to add tests, write tests, cover code, or increase coverage.