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.
git clone --depth 1 https://github.com/signalcompose/claude-toolsWrote 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/commands/signalcompose/claude-tools/pr-review-team)<a href="https://agentmods.dev/commands/signalcompose/claude-tools/pr-review-team"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/pr-review-team/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/commands/signalcompose/claude-tools/pr-review-team"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/pr-review-team.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.00013 | $0.00565 |
| Opus 5 | $0.00006 | $0.00282 |
| Sonnet 5 | $0.00003 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
pr-review-team 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
PR Review Team
チーム編成による PR レビュー。変更ファイルの種別に応じて最大4つの専門エージェントを条件起動し、CI 結果と統合して反復的に修正。
使い方
/code:pr-review-team [PR番号]
PR番号を省略すると、現在のブランチに紐づく PR を自動検出します。
ワークフロー
- 対象PR特定 — PR番号の解決、プロジェクトコンテキスト検出
- レビューチーム作成 —
select-reviewers.shで変更ファイル種別を判定し、必要な専門レビュアーのみ並行起動（docs/config のみの PR は不要なレビュアーをスキップ）- code-reviewer: コード品質・バグ検出（常時起動）
- silent-failure-hunter: サイレント障害・エラーハンドリング（コード変更時）
- pr-test-analyzer: テストカバレッジ分析（コード変更時）
- comment-analyzer: コメント正確性検証（コード/ドキュメント変更時）
- CI結果収集 —
gh pr checksで CI 状態を取得、失敗ログ分析 - 統合・修正 — レビュー結果 + CI 結果を fixer に一括送信（Codex を利用可能なら優先し、利用不可時は従来どおり Sonnet にフォールバック）
- 反復ループ — Critical/Important = 0 かつセキュリティ全合格まで（最大3回）。ラウンド2以降は code-reviewer、直前ラウンドで問題を報告した reviewer、および selector の新規追加分のみ再起動
- 完了報告 — サマリー表示、マージはユーザー指示待ち
完了条件
- Critical 問題 = 0
- Important 問題 = 0
- セキュリティチェックリスト全項目合格
関連
- merge 前チェックリスト:
/code:checkup（merge 前に確認したい項目を surface） - リファクタリング:
/code:refactor-team（PR非依存のコード改善）
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 · 40 lines · 13 tokens per session scan A ff84b47ff6cd
pr-review-team is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 12d ago), licensed MIT. It adds 13 tokens to every session and 565 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 commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.