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 morodomi/tdd-skills --skill tdd-parallelgit clone --depth 1 https://github.com/morodomi/tdd-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/morodomi/tdd-skills/tdd-parallel)<a href="https://agentmods.dev/skills/morodomi/tdd-skills/tdd-parallel"><img src="https://agentmods.dev/badge/skills/morodomi/tdd-skills/tdd-parallel/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/morodomi/tdd-skills/tdd-parallel"><img src="https://agentmods.dev/badge/skills/morodomi/tdd-skills/tdd-parallel.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.00052 | $0.00871 |
| Opus 5 | $0.00026 | $0.00436 |
| Sonnet 5 | $0.00010 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
tdd-parallel 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 Parallel - Cross-Layer Parallel Development
Agent Teams でレイヤー別に RED/GREEN/REFACTOR を並列実行するオーケストレータ。
Architecture Note
このスキルは例外的に複数フェーズ(RED/GREEN/REFACTOR)をまたぐが、 内部では既存の単一フェーズ Skill を Teammate が順次実行する。 7フェーズモデル自体は維持される（合成パターン）。
When to Use
| 条件 | 推奨 |
|---|---|
| 3+ レイヤー、API契約変更あり | tdd-parallel |
| 単一レイヤー、2ファイル以下 | 通常 TDD (tdd-red → tdd-green → tdd-refactor) |
Progress Checklist
tdd-parallel Progress:
- [ ] Agent Teams 確認
- [ ] レイヤー定義確認・ファイル分離検証
- [ ] レイヤー別 Teammate 起動 (RED→GREEN→REFACTOR)
- [ ] 統合テスト実行・全レイヤー GREEN 確認
- [ ] REVIEW 自動実行
Workflow
Step 1: Agent Teams 確認
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS 環境変数をチェック:
| 環境変数 | アクション |
|---|---|
有効 (1) |
Step 2 へ |
| 無効 / 未設定 | エラー表示、通常 TDD を推奨して終了 |
無効時: steps-teams.md Fallback のメッセージを表示して終了。
Step 2: レイヤー定義確認
Cycle doc から In Scope のレイヤー情報を読取:
| レイヤー数 | アクション |
|---|---|
| 1 | 中止、通常 TDD を推奨 |
| 2-4 | Step 3 へ |
| 5+ | 警告、レイヤー統合を推奨 |
| レイヤー例 | ファイル範囲 | テスト範囲 |
|---|---|---|
| Backend | src/api/, models/ | tests/api/ |
| Frontend | src/components/ | tests/components/ |
| Database | migrations/ | tests/db/ |
詳細: reference.md
Step 3: 並列開発実行
steps-teams.md の手順に従い実行。
各 Teammate が Skill(tdd-core:tdd-red) → Skill(tdd-core:tdd-green) → Skill(tdd-core:tdd-refactor) を順次実行。
Step 4: 統合テスト
全レイヤーの GREEN 確認後、全テスト一括実行:
# 全テスト実行（プロジェクト依存）
pytest # Python
npm test # JS/TS
php artisan test # PHP
失敗時: テスト出力からレイヤー特定 → 該当 Teammate に修正指示。
Step 5: 完了 → REVIEW 自動実行
tdd-parallel 完了。全レイヤー GREEN、統合テスト PASS。
REVIEW フェーズを自動実行します。
Skill(tdd-core:tdd-review) を実行。
Reference
- 詳細: reference.md
- オーケストレーション: steps-teams.md
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 96 lines · 52 tokens per session scan A 537f27b88012
tdd-parallel is a skill published in the GitHub repository morodomi/tdd-skills (8 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 871 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-31.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.