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-onboardgit 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-onboard)<a href="https://agentmods.dev/skills/morodomi/tdd-skills/tdd-onboard"><img src="https://agentmods.dev/badge/skills/morodomi/tdd-skills/tdd-onboard/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-onboard"><img src="https://agentmods.dev/badge/skills/morodomi/tdd-skills/tdd-onboard.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.00062 | $0.00821 |
| Opus 5 | $0.00031 | $0.00411 |
| Sonnet 5 | $0.00012 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade B, and why
tdd-onboard scanned grade B with 1 finding 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 11d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Hook設定の案内: `.claude/hooks/recommended.md` に推奨Hook設定が記載されている旨をユーザーに伝え、`~/.claude/settings.json` にコピーしてClaude Codeを再起動するよう案内する。 What it actually says
TDD Onboard
既存プロジェクトにTDD環境をセットアップする。
Progress Checklist
コピーして進捗を追跡:
Onboard Progress:
- [ ] プロジェクト分析（フレームワーク/テストツール検出）
- [ ] 検出結果をユーザーに確認
- [ ] docs/ 構造作成（cycles/, README.md, STATUS.md）
- [ ] CLAUDE.md 生成（既存あればマージ）
- [ ] 階層CLAUDE.md推奨（任意）
- [ ] .claude/ 構造生成（rules/, hooks/）
- [ ] Pre-commit Hook確認（推奨）
- [ ] 初期Cycle doc作成
- [ ] Next Steps 表示
Workflow
Step 1: プロジェクト分析
フレームワークとツールを検出:
ls artisan 2>/dev/null # Laravel
ls app.py wsgi.py 2>/dev/null # Flask
ls wp-config.php 2>/dev/null # WordPress
ls composer.json package.json pyproject.toml 2>/dev/null
Step 2: 検出結果確認
AskUserQuestion で確認:
- フレームワーク
- パッケージマネージャ
- 既存CLAUDE.mdの処理方法
Step 3: docs/ 構造作成
mkdir -p docs/cycles
作成ファイル:
docs/README.md- ドキュメント索引docs/STATUS.md- プロジェクト状況（tdd-commitで自動更新）
テンプレートは reference.md を参照。
Step 4: CLAUDE.md 生成
- 既存あり → マージ or 上書き確認
- 既存なし → テンプレートから生成
テンプレートとマージ戦略は reference.md を参照。
Step 5: 階層CLAUDE.md推奨（任意）
tests/, src/, docs/ に CLAUDE.md 配置を推奨（各30-50行）。 詳細は reference.md を参照。
Step 6: .claude/ 構造生成
存在しない場合に作成。rules/: git-safety, security, git-conventions。hooks/: recommended。推奨設定: Skill(tdd-core:*) をallowedToolsに追加。詳細は reference.md。
Hook設定の案内: .claude/hooks/recommended.md に推奨Hook設定が記載されている旨をユーザーに伝え、~/.claude/settings.json にコピーしてClaude Codeを再起動するよう案内する。
Step 7: Pre-commit Hook確認（推奨）
hookなし → セットアップ推奨。詳細は reference.md を参照。
Step 8: 初期Cycle doc作成
docs/cycles/YYYYMMDD_0000_project-setup.md を作成。
Step 9: 完了
セットアップ完了メッセージを表示。次: tdd-init で開発開始。
Reference: reference.md
What ships with it
1 file 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.
- 11d ago First seen · 90 lines · 62 tokens per session scan B 4147593eef2d
tdd-onboard is a skill published in the GitHub repository morodomi/tdd-skills (8 stars, last pushed 7mo ago), licensed MIT. It adds 62 tokens to every session and 821 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
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.