Borrowing it
Nothing to install: this file belongs to ffroliva/gflow-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ffroliva/gflow-cli/develop/.claude/commands/gflow/branch-review.mdgit clone --depth 1 https://github.com/ffroliva/gflow-cliWrote 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/ffroliva/gflow-cli/branch-review)<a href="https://agentmods.dev/commands/ffroliva/gflow-cli/branch-review"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/branch-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/commands/ffroliva/gflow-cli/branch-review"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/branch-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.00072 | $0.00310 |
| Opus 5.5 | $0.00029 | $0.00124 |
| Sonnet 5.5 | $0.00014 | $0.00062 |
| Haiku 4.5 | $0.00007 | $0.00031 |
Grade A, and why
branch-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 1mo 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
/gflow:branch-review [--base <ref>]
Read skills/pr-council-review/SKILL.md and follow its protocol now in BRANCH MODE (§ 8), passing $ARGUMENTS (optional --base <ref>; default develop).
Do not call
Skill(skill="pr-council-review")— the repo'sskills/*/SKILL.mdfiles are plain Markdown, not registered as Skill-tool-invocable (only.claude/commands/gflow/*are). Invoking it errors withUnknown skill: pr-council-review. Read the file directly instead.
The canonical body is skills/pr-council-review/SKILL.md. § 8 documents branch-mode-specific behavior: pre-flight, the PR→branch translation table, release/* downgrade, SHA drift, and local-only output. All other phases (gather context, detect dimensions, dispatch, synthesize, report) are identical to PR mode.
Sibling: /gflow:pr-council-review <N> runs the same council against an open 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.
- 1mo ago First seen · 14 lines · 72 tokens per session scan A 189cf4b76b76
branch-review is a command published in the GitHub repository ffroliva/gflow-cli (337 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 310 once invoked, about $0.0003 per session on Opus 5.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
lint
Check the project for naming, security and best-practice issues.
review
Review the branch's changes against the CLAUDE.md PR checklist.
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
hatch3r-rework
User-guided rework planning for agent-implemented code in a fresh context window. Reconstructs what was delivered from the git diff, interviews the user for feedback, triages findings, validates them read-only against the code, and ends at a rework plan (docs/rework/) plus an execute-now-or-defer choice (copy-paste…
proposal
Create a structured feature proposal in docs/11-proposals/.
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.