Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/morodomi/tdd-skillsnpx agentmods add skills/morodomi/tdd-skills/tdd-reviewWrote 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-review)<a href="https://agentmods.dev/skills/morodomi/tdd-skills/tdd-review"><img src="https://agentmods.dev/badge/skills/morodomi/tdd-skills/tdd-review/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-review"><img src="https://agentmods.dev/badge/skills/morodomi/tdd-skills/tdd-review.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.00050 | $0.00701 |
| Opus 5 | $0.00025 | $0.00351 |
| Sonnet 5 | $0.00010 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
tdd-review 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 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.
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 REVIEW Phase
最終的な品質検証を行う。
Progress Checklist
コピーして進捗を追跡:
REVIEW Progress:
- [ ] テスト実行（全PASS）
- [ ] カバレッジチェック（目標達成）
- [ ] 静的解析実行（エラー0件）
- [ ] quality-gate 実行（必須・スキップ不可）
- [ ] コードフォーマッタ実行
- [ ] DISCOVERED issue 起票（該当項目がある場合）
- [ ] Cycle doc更新
- [ ] COMMITフェーズへ誘導
品質基準
| 項目 | 目標 | 最低ライン |
|---|---|---|
| テスト | 全PASS | 全PASS |
| カバレッジ | 90%+ | 80% |
| 静的解析 | エラー0 | エラー0 |
| quality-gate | PASS | WARN以下 |
Workflow
Step 1: テスト実行
php artisan test # PHP / pytest # Python
Step 2: カバレッジ確認
php artisan test --coverage --min=80 # PHP
pytest --cov=src --cov-fail-under=80 # Python
Step 3: 静的解析
./vendor/bin/phpstan analyse --level=8 # PHP
mypy --strict src/ # Python
Step 4: quality-gate（必須・スキップ不可）
quality-gateスキルを必ず実行する。スキップ不可。4エージェントで並行レビュー。
- PASS（スコア49以下） → Step 5へ
- WARN（スコア50-79） → 警告確認後、Step 5へ
- BLOCK（スコア80以上） → GREENに戻って修正
Step 5: フォーマッタ
./vendor/bin/pint # PHP
black . && isort . # Python
Step 6: DISCOVERED issue 起票
Cycle doc の DISCOVERED セクションを確認し、スコープ外の未起票項目を GitHub issue に起票する。 DISCOVERED が空の場合はスキップ。詳細: reference.md
Step 7: 品質基準クリア確認
結果を表示し、ユーザー承認を求める。COMMIT判断はユーザーが行う。
REVIEW完了。quality-gate: [PASS/WARN/BLOCK]
COMMITしますか？
Reference
- 詳細: reference.md
- quality-gate: ../quality-gate/SKILL.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 · 50 tokens per session scan A 48691a7dbc8e
tdd-review is a skill published in the GitHub repository morodomi/tdd-skills (8 stars, last pushed 7mo ago), licensed MIT. It adds 50 tokens to every session and 701 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
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
gentle-ai
Use Gentle AI harness discipline for Pi work: clarify first, preserve OpenSpec artifacts, use strict TDD where available, delegate through subagents when useful, and protect review workload.
software-test-review
Evaluate the quality of TDD tests against slice acceptance criteria, codebase conventions, and Red-phase execution results, producing a structured review with Accept or Revise recommendations. Use when tests written during the Red phase of red-green-refactor need quality review — checking coverage of acceptance…
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
quality-playbook
Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches.…