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 plan-reviewgit 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/plan-review)<a href="https://agentmods.dev/skills/morodomi/tdd-skills/plan-review"><img src="https://agentmods.dev/badge/skills/morodomi/tdd-skills/plan-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/plan-review"><img src="https://agentmods.dev/badge/skills/morodomi/tdd-skills/plan-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.00028 | $0.00513 |
| Opus 5 | $0.00014 | $0.00257 |
| Sonnet 5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
plan-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 10d 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
Plan Review
PLANフェーズの設計を5つの専門エージェントで並行レビューする。
Progress Checklist
plan-review Progress:
- [ ] Cycle doc確認
- [ ] レビュー実行（Subagent + Sonnet）
- [ ] 結果統合・スコア判定
- [ ] 分岐判定（PASS/WARN/BLOCK）
Workflow
Step 1: Cycle doc確認
ls -t docs/cycles/*.md 2>/dev/null | head -1
PLANセクション（設計方針、Test List、変更予定ファイル）を読み込む。
Step 2: レビュー実行
Subagent + Sonnet で並行実行。手順: steps-subagent.md
Step 3: 結果統合
各エージェントの信頼スコアを集計:
| 最大スコア | 判定 | アクション |
|---|---|---|
| 80-100 | BLOCK | 修正必須、進行不可 |
| 50-79 | WARN | 警告表示、継続可能 |
| 0-49 | PASS | 問題なし |
Step 4: 分岐判定
PASS（スコア49以下）
設計レビュー完了。問題ありません。
→ REDフェーズへ進んでください
WARN（スコア50-79）
警告があります。確認してください。
1. 警告を確認してREDへ進む
2. PLANに戻って修正
BLOCK（スコア80以上）
重大な問題が検出されました。
→ PLANに戻って修正してください
（Progress Logに記録済み）
Cycle docのProgress Logに以下の形式で追記する:
- YYYY-MM-DD HH:MM [PLAN] plan-review BLOCK (score NN): reviewer「指摘要約」
Reference
- エージェント定義:
../../agents/ - スコアリング・出力形式: reference.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.
- 10d ago First seen · 75 lines · 28 tokens per session scan A fc1540c79ecf
plan-review is a skill published in the GitHub repository morodomi/tdd-skills (8 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 513 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
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.