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 masa-san-jp/Agent-Aiko --skill pr-review-mergegit clone --depth 1 https://github.com/masa-san-jp/Agent-AikoWrote 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/masa-san-jp/agent-aiko/pr-review-merge)<a href="https://agentmods.dev/skills/masa-san-jp/agent-aiko/pr-review-merge"><img src="https://agentmods.dev/badge/skills/masa-san-jp/agent-aiko/pr-review-merge/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/masa-san-jp/agent-aiko/pr-review-merge"><img src="https://agentmods.dev/badge/skills/masa-san-jp/agent-aiko/pr-review-merge.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.00135 | $0.00862 |
| Opus 5 | $0.00068 | $0.00431 |
| Sonnet 5 | $0.00027 | $0.00172 |
| Haiku 4.5 | $0.00014 | $0.00086 |
Grade A, and why
pr-review-merge 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
/pr-review-merge
PR 作成後の標準フロー。PR を作って放置しない。 作成後はこのフローを最後（マージ or 報告）まで同一ターンで完走する。
実行手順
1. PR を作成し、URL と番号を控える
gh pr create --base <target> --head <branch> --title ... --body ...（または既存 PR 番号）。
2. 数分待つ
CI とレビュー（人／bot／自動レビュー）が付くのを待つ。ポーリングはバックグラウンドで（会話を止めない）：
# 数分後にチェックを促す待機（バックグラウンド）
( sleep 300 ) & # 実運用は Bash run_in_background / スケジュール待機機構を使う
待機中に他の作業を進めてよい。CI が早く終われば早めに次へ進んでよい。
3. レビューを確認（CI＋コメント＋マージ可否）
gh pr checks <num> # CI: 全部 pass か（fail/pending を見る）
gh pr view <num> --json reviews,comments,mergeable,mergeStateStatus
gh pr view <num> --comments # レビューコメント本文
確認軸：① CI が緑 ② レビュー指摘が無い（あれば対応） ③ コンフリクトが無い（mergeable）。
4. 問題があれば修正
- CI fail：原因を実機で再現・修正してコミット＆push → checks 再確認。
- レビュー指摘：対応してコミット＆push。対応内容を PR にコメントで残す。
- コンフリクト：rebase／merge で解消。
- 修正したら 手順 2〜3 をもう一度（再度 CI／レビューを待って確認）。
5. 問題なければマージ
gh pr merge <num> --squash --delete-branch # 既定は squash。プロジェクト規約があれば従う
不可逆操作なので、CI 緑・指摘なし・mergeable を確認してから実行する。 マージ可否に疑義がある（レビュー未着・CI 不明・大きめの変更）ときはマージせず、状態をオーナーに報告して指示を仰ぐ。
6. 報告
マージ結果（または現状：CI・レビュー・マージ可否）を必ずオーナーに報告する。失敗は失敗と正直に。
メモ
- 待ち時間（例：数分）はプロジェクトの CI 実行時間に合わせて調整する。
- 待ち時間中も webhook activity が届いたら即調査・対応する（待つ＝放置ではない）。
ghが無い／権限が無い環境では、その旨を報告して手動マージを案内する。
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 · 62 lines · 135 tokens per session scan A 4b7b351189b8
pr-review-merge is a skill published in the GitHub repository masa-san-jp/Agent-Aiko (3 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 862 once invoked, about $0.0007 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
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
pr-body
A tool that reviews all commits on the current branch and creates or updates a pull request title and description. A pull request is a proposed code change submitted for review.
ghx
Guidance for safe, reliable GitHub CLI workflows across issues, pull requests, and reviews.
github-pr-fix
Fix a GitHub pull request by addressing feedback or CI failures, pushing changes, and publishing replies.
github-pr-comment
Post one exact GitHub pull-request comment through local gh, any compatible hosted connector, or the explicit human-gated MCP composition, with retry safety and independent readback.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…