What is uf.review-council?

A command that runs a structured review of a codebase or specification against its rules. It gathers findings, checks review status, and asks for confirmation before posting a review.

Use it to audit code changes, compare them with a specification, consolidate review findings, and guide fixes through several review rounds.

It reduces the chance that important compliance issues are missed or that review comments are posted without human approval.

How unbound-force/gaze configures Claude Code and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to unbound-force/gaze. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/unbound-force/gaze/main/.opencode/commands/uf.review-council.md

Clone the repo

git clone --depth 1 https://github.com/unbound-force/gaze

Made for: Claude Code, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/unbound-force/gaze/uf.review-council/github.svg)](https://agentmods.dev/commands/unbound-force/gaze/uf.review-council)

Your own site

<a href="https://agentmods.dev/commands/unbound-force/gaze/uf.review-council"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/uf.review-council/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/unbound-force/gaze/uf.review-council"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/uf.review-council.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 15,150 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.15150
Opus 5.5	$0.00005	$0.06060
Sonnet 5.5	$0.00003	$0.03030
Haiku 4.5	$0.00001	$0.01515

Measured 2d ago against content hash 46fde4654072, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

uf.review-council 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 2d 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.

.opencode/commands/uf.review-council.md · 1,466 lines

How it starts

The opening of the file, as written. The whole thing — 1,466 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Command: /uf.review-council

Session-resume guard: If this session was resumed from compressed context, re-read this entire template before continuing. Do NOT infer step completion from compressed summaries. Call get_progress with command: "uf.review-council" to recover actual completion state. Resume from the first incomplete step. When in doubt, re-read — false re-reads are harmless; skipping steps due to stale context causes incomplete reviews or unauthorized actions.

PROGRESS TRACKING — On startup, call get_progress with command: "uf.review-council" to recover any prior state. After completing each phase or step, call checkpoint with command: "uf.review-council" and the appropriate step name to persist progress. At the final step (7g), also call clear_progress with command: "uf.review-council" to clean up state.

Checkpoint Progress Tracking

Use the checkpoint tool for persistent progress tracking. After completing each phase or step, call checkpoint with command: "uf.review-council" and the step name (e.g., step: "phase-1a-preflight"). This persists progress across session boundaries and context compression.

On resume from compressed context, call get_progress with command: "uf.review-council" to recover the last completed step. Resume from the first incomplete step.

TodoWrite Progress Tracking

Use the TodoWrite tool for live session visibility. At command start, initialize TodoWrite with all phases and steps as pending. Before starting each phase, mark it in_progress. After completing each phase, mark it completed. This runs alongside the checkpoint tool progress tracking — both MUST be maintained.

On resume from compressed context, call get_progress with command: "uf.review-council" and re-initialize the TodoWrite list from the returned state: completed_steps entries become completed, the current_step becomes in_progress, and remaining steps become pending.

Read the full file on GitHub · 1,466 lines

Changes

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.

2d ago Changed · +56 lines 46fde4654072
3d ago Changed · +67 lines 7b1841beae9c
8d ago Changed · +407 lines 934b0304f9d2
1mo ago Changed 91cc455384fb
2mo ago Changed · +60 lines f3c7bfa4f536
2mo ago First seen · 876 lines · 13 tokens per session scan A 7c2e3a1b081d

Subscribe to this mod's changes

uf.review-council is a command published in the GitHub repository unbound-force/gaze (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 15,150 once invoked, about $0.0001 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-31.

Code review

uf.review-council next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
uf.review-councilunbound-force/gaze	Command	4	yesterday	Apache-2.0	A	13	Claude Code, OpenCode
diff-reviewcoco-research/coco	Command	785	yesterday	Apache-2.0	A	11	Claude Code
review-branchdamusix/atomic-claude	Command	115	4d ago	MIT	A	35	Claude Code
refactorRchGrav/claudebox	Command	1.2k	1mo ago	MIT	A	9	Claude Code
spec-trace-requirementsrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
initazrtydxb/procoder	Command	211	11d ago	Apache-2.0	A	16	Claude Code

gaze: Command for Claude Code