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 commands/kewton/commandmate/multi-stage-issue-reviewgit clone --depth 1 https://github.com/Kewton/CommandMateWrote 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/kewton/commandmate/multi-stage-issue-review)<a href="https://agentmods.dev/commands/kewton/commandmate/multi-stage-issue-review"><img src="https://agentmods.dev/badge/commands/kewton/commandmate/multi-stage-issue-review.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.04261 |
| Opus 5 | $0.00015 | $0.02131 |
| Sonnet 5 | $0.00006 | $0.00852 |
| Haiku 4.5 | $0.00003 | $0.00426 |
Grade A, and why
multi-stage-issue-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
マルチステージIssueレビューコマンド
概要
Issueの記載内容を多角的にレビューし、ブラッシュアップするコマンドです。 通常レビューと影響範囲レビューを2回ずつ実施し、各段階でレビュー→反映のサイクルを回します。
目的: Issueの品質を段階的に向上させ、実装前に問題点を洗い出す
使用方法
/multi-stage-issue-review [Issue番号]
/multi-stage-issue-review [Issue番号] --skip-stage=5,6,7,8
例:
/multi-stage-issue-review 83 # 全8段階を実行
/multi-stage-issue-review 83 --skip-stage=5,6,7,8 # 1回目のみ実行
実行内容
あなたはマルチステージIssueレビューの統括者です。8段階のレビューサイクルを順次実行し、各段階で指摘事項を対応してから次の段階に進みます。
パラメータ
- issue_number: 対象Issue番号（必須）
- skip_stage: スキップするステージ番号（カンマ区切り）
サブエージェント/レビュアー指定
| ステージ | レビュアー | 理由 |
|---|---|---|
| Stage 1-4（1回目） | Claude opus（サブエージェント） | 品質判断にOpus必要 |
| Stage 5-8（2回目） | Codex（commandmatedev --agent codex 経由） |
異なるモデルによるクロスレビュー |
| 指摘反映（全ステージ） | sonnet（継承） | JSON→Issue更新のみ |
⚠ 重要: Stage 5-8 は必ず
commandmatedev send ... --agent codexでCodexに委譲すること。 Claude サブエージェント（Agent tool）で代替実行してはならない。 commandmatedev が利用不可の場合はユーザーに報告して中断すること。
レビューステージ
| Phase/Stage | レビュー種別 | フォーカス | 目的 |
|---|---|---|---|
| 0.5 | 仮説検証 | コードベース照合 | Issue内の仮説・原因分析を実コードで検証 |
| 1 | 通常レビュー（1回目） | 整合性・正確性 | 既存コード/ドキュメントとの整合性確認 |
| 2 | 指摘事項反映（1回目） | - | Stage 1の指摘をIssueに反映 |
| 3 | 影響範囲レビュー（1回目） | 影響範囲 | 変更の波及効果分析 |
| 4 | 指摘事項反映（1回目） | - | Stage 3の指摘をIssueに反映 |
| 5 | 通常レビュー（2回目） | 整合性・正確性 | 更新後のIssueを再チェック |
| 6 | 指摘事項反映（2回目） | - | Stage 5の指摘をIssueに反映 |
| 7 | 影響範囲レビュー（2回目） | 影響範囲 | 更新後の影響範囲を再チェック |
| 8 | 指摘事項反映（2回目） | - | Stage 7の指摘をIssueに反映 |
実行フェーズ
Phase 0: 初期設定
0-1. TodoWriteで作業計画作成
- [ ] Phase 0.5: 仮説検証
- [ ] Stage 1: 通常レビュー（1回目）
- [ ] Stage 2: 指摘事項反映（1回目）
- [ ] Stage 3: 影響範囲レビュー（1回目）
- [ ] Stage 4: 指摘事項反映（1回目）
- [ ] Stage 5: 通常レビュー（2回目）
- [ ] Stage 6: 指摘事項反映（2回目）
- [ ] Stage 7: 影響範囲レビュー（2回目）
- [ ] Stage 8: 指摘事項反映（2回目）
- [ ] 最終確認
0-2. ディレクトリ構造作成
mkdir -p dev-reports/issue/{issue_number}/issue-review
0-3. 初期Issue内容のバックアップ
gh issue view {issue_number} --json title,body > dev-reports/issue/{issue_number}/issue-review/original-issue.json
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.
- 4d ago First seen · 386 lines · 30 tokens per session scan A 751b13a2924d
multi-stage-issue-review is a command published in the GitHub repository Kewton/CommandMate (39 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 4,261 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-30.
Other commands, from other repositories
crow-image
Show an image in Crow's Images panel — pass the file path as the argument.
release-notes
Draft release notes, recommend and apply a version bump, and update CHANGELOG.md for the next dormouse release by analyzing all merge commits and squash-merged PRs since the last release tag. Used as step 2 of the release checklist in docs/specs/deploy.md.
build-docs
Build and serve the docs site locally with Jekyll.
release
Cut a domux release — tag HEAD, push, watch the GH Action.
review-session-log
Use when the user asks what a session did, wants to review session history, or needs to find errors in a session log.
setup
Install & set up newsline — rotating regional news in your status line (keeps your existing status line).