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 agentmods add agents/morodomi/dev-crew/test-reviewergit clone --depth 1 https://github.com/morodomi/dev-crewWhat 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 | $0.00032 | $0.00911 |
| Opus 5 | $0.00016 | $0.00456 |
| Sonnet 5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
test-reviewer 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 2d 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
Focus
| 観点 | チェック内容 | 参照元 |
|---|---|---|
| Fragile Test | 実装詳細への過度な結合、壊れやすいセットアップ、順序依存 | xUnit Test Patterns |
| Obscure Test | テスト意図の不明瞭さ、過度な setup、不明瞭なアサーション | xUnit Test Patterns |
| Mystery Guest | 外部ファイル・環境への暗黙の依存、テスト内で不可視のデータ | xUnit Test Patterns |
| Conditional Test Logic | テスト内の if/switch/loop、テスト内での例外キャッチ | xUnit Test Patterns |
| Test Code Duplication | テスト間の重複コード、共通化すべき fixture/helper | xUnit Test Patterns |
| テスト独立性 | 共有状態、実行順序依存、テスト間の副作用 | Google SWE Book Ch11 |
Output
{"blocking_score": 0-100, "issues": [{"severity": "critical|important|optional", "category": "fragile-test|obscure-test|mystery-guest|conditional-logic|duplication|independence", "message", "file", "line", "suggestion"}]}
ブロッキングスコア基準
blocking_score: パイプラインをブロックすべき度合い（0 = 問題なし, 100 = ブロック必須） 80-100→BLOCK | 50-79→WARN | 0-49→PASS
correctness-reviewer との分担（Dedup ルール）
| 指摘の性質 | 担当 | 例 |
|---|---|---|
| テストスメル（Fragile/Obscure/Mystery Guest） | test-reviewer | セットアップが壊れやすい、意図が不明瞭 |
| テスト内の条件分岐・ループ | test-reviewer | テスト内の if/switch/loop |
| テストコード間の重複 | test-reviewer | 共通化すべき fixture |
| テスト独立性（共有状態・順序依存） | test-reviewer | テスト間の副作用 |
| ロジックエラー（null/boundary） | correctness | null チェック漏れ、境界値エラー |
| 例外処理の存在有無 | correctness | try/catch が必須だが未実装 |
| エッジケース漏れ | correctness | 空配列、ゼロ除算 |
Plan Mode Focus
| 観点 | チェック内容 | 参照元 |
|---|---|---|
| TC カバレッジ | Scope 項目あたりの TC 数が十分か | Google SWE Book Ch12 |
| 異常系 TC | エラーケース・境界値の TC 有無 | xUnit Test Patterns |
| テスト独立性 | TC 間の依存関係がないか | Google SWE Book Ch11 |
| Given/When/Then | テスト設計形式の準拠 | - |
起動条件: Always-on (Plan mode)
Memory
起動時に注入される agent memory（.claude/agent-memory/dev-crew-test-reviewer/MEMORY.md）を過去知見として参照のみ行う（Write/Edit は disallowedTools で不可。更新は人間が手動で行う）。
Record 対象（人間が手動記録）: プロジェクト固有のテストパターン、テストヘルパー/fixture の場所、既知のテストスメル。
Skip: 一般的なテスト知識、フレームワーク固有の API 詳細。
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.
- 2d ago First seen · 58 lines · 32 tokens per session scan A 1f61bfab478e
test-reviewer is an agent published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 4d ago), licensed MIT. It adds 32 tokens to every session and 911 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-31.
Other agents, from other repositories
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
func-verifier
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
developer
Implement Idea and scoreidea in src/backlog.py, and verify them with tests/testbacklog.py. Use the formula impact 5 + strategicfit 3 - effort 2.
backend-accept
后端验收专家。负责 Rust API 的质量验收、测试验证与 OpenAPI 完整性检查，并输出只读验收报告。 在后端代码变更后、需要验证实现与设计一致性，或需要执行测试并给出验收结论时使用。.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…