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/ffroliva/gflow-cli/pr-council-reviewgit 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/pr-council-review)<a href="https://agentmods.dev/commands/ffroliva/gflow-cli/pr-council-review"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/pr-council-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.1 | $0.00079 | $0.00374 |
| Opus 5 | $0.00039 | $0.00187 |
| Sonnet 5 | $0.00016 | $0.00075 |
| Haiku 4.5 | $0.00008 | $0.00037 |
Grade A, and why
pr-council-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 6d 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:pr-council-review [PR#]
Read skills/pr-council-review/SKILL.md and follow its protocol now, treating $ARGUMENTS as the PR number (or empty for prioritize-mode). That file is the canonical body: preflight, dimension detection, parallel dispatch, synthesis, report.
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.
Required gate — SonarCloud must be green. The council reviews the diff; it does
not see SonarCloud's verdict. Before declaring the final verdict, run /gflow:sonar
for this PR — the SonarCloud analysis gate must be green (zero new issues). A red gate
is a blocking finding regardless of the council's own conclusions; report it with the
exact failing conditions and do not call the PR merge-ready until it is green.
Sibling: /review is the single-agent Claude-Code built-in (fast, one-pass). Use it for spot-checks; use this command for pre-merge multi-dim audits.
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.
- 6d ago First seen · 18 lines · 79 tokens per session scan A af43a150ee31
pr-council-review is a command published in the GitHub repository ffroliva/gflow-cli (156 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 374 once invoked, about $0.0004 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
critique-screen
Run all seven visual critiques on a screen and output a prioritised fix list.
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
dashboard-session-diff
Show file changes (git diff) for a session by id-prefix. Usage /dashboard:session-diff . Runs locally, no LLM.
dashboard-session-list
List all pi sessions (id, status, name, cwd). Runs locally, no LLM.
pipeline-undo
Undo a pipeline run's result. With worktree isolation (the current engine), this is clean and low-risk: a run never touches your checkout — its result lives only on a pipeline/ branch (and, for a --push run, on the remote). "Undo" therefore means deleting that branch and its worktree, not reverting your working tree.