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 skills add cafe3310/public-agent-skills --skill tdd-dev-cyclegit clone --depth 1 https://github.com/cafe3310/public-agent-skillsWrote 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/cafe3310/public-agent-skills/tdd-dev-cycle)<a href="https://agentmods.dev/skills/cafe3310/public-agent-skills/tdd-dev-cycle"><img src="https://agentmods.dev/badge/skills/cafe3310/public-agent-skills/tdd-dev-cycle/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/cafe3310/public-agent-skills/tdd-dev-cycle"><img src="https://agentmods.dev/badge/skills/cafe3310/public-agent-skills/tdd-dev-cycle.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.00038 | $0.00643 |
| Opus 5 | $0.00019 | $0.00321 |
| Sonnet 5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
tdd-dev-cycle 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.
What it actually says
TDD (测试驱动开发) 主干工作循环
本 Skill 定义了标准的 TDD 开发与验证循环。
适用场景
如果项目章程没有定义具体的工作流，助手默认遵循以下 TDD 主干工作循环。
流程详情
-
智能调度
- 优先处理 backlog 中
priority: high的任务。 - 在选定了任务后，将其从
docs/backlog/移动到docs/requirements/并更新状态为开发中，然后开始分析。
- 优先处理 backlog 中
-
规划与澄清 (TDD)
- a. 分析需求: 如果模糊则提问，并更新需求文档。
- b. 解决冲突: 如果需求和项目级别章程冲突，则提问澄清如何处理。一般来说要更新章程中的设计。
- c. 定义验收标准: 优先编写自动化测试用例。
- d. COMMIT 1:
git commit -m "完成需求 {文件名} 的分析与测试用例，即将开发"
-
开发
- 根据测试用例进行编码实现。
-
开发完成 -> COMMIT
- COMMIT 2:
git commit -m "完成需求 {文件名} 的开发，即将验证"
- COMMIT 2:
-
验证与带熔断的修复循环
- a. 运行自动化测试。
- b. 成功:
- COMMIT 5:
git commit -m "需求 {文件名} 的开发和验证已经全部完成！" - 报告完成并循环。
- COMMIT 5:
- c. 失败 (第 N 次):
- COMMIT 3:
git commit -m "验证需求 {文件名} 时遇到问题 {问题描述} (第 N 次尝试)，即将修复" - 熔断检查: 若 N > 3 次，则触发熔断，停止，并向用户求助。
- 修复: 分析日志，定位原因，编写修复代码。
- COMMIT 4:
git commit -m "验证需求 {文件名} ，成功解决了问题 {问题描述} (第 N 次尝试)" - 返回步骤 5a 重新验证。
- COMMIT 3:
循环直至所有 backlog 任务完成、用户打断、指令变更或达到熔断条件。
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 · 46 lines · 38 tokens per session scan A 1828d4f5cc2d
tdd-dev-cycle is a skill published in the GitHub repository cafe3310/public-agent-skills (253 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 643 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 skills, from other repositories
springboot-tdd
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
test-driven-development
Use when implementing new features or fixing bugs. Write tests before implementation following Red-Green-Refactor. Covers JUnit5, MockK, Compose test rules, and the Prove-It pattern for bugs.
obsidian-development
Expert guidance for the entire Obsidian plugin development lifecycle. Use this skill when building, testing, or releasing Obsidian plugins. It mandates TDD with Vitest, adherence to the Obsidian API, and automated CI/CD via GitHub Actions.
django-tdd
Django testing strategies with pytest-django, TDD methodology, factoryboy, mocking, coverage, and testing Django REST Framework APIs.
python-testing
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.