What is consistency-review?

An interactive command for reviewing findings from a consistency-check report one at a time.

Run /consistency-review with a date, or without one for the latest report, to triage findings and update the precision tally.

It keeps the final decision with the person reviewing the report and records whether each finding should be accepted, rejected, deferred, or marked false.

How jaroslavsoucek-art/Giovanni configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jaroslavsoucek-art/Giovanni. 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/jaroslavsoucek-art/Giovanni/main/.claude/commands/consistency-review.md

Clone the repo

git clone --depth 1 https://github.com/jaroslavsoucek-art/Giovanni

Made for: Claude Code.

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/jaroslavsoucek-art/giovanni/consistency-review/github.svg)](https://agentmods.dev/commands/jaroslavsoucek-art/giovanni/consistency-review)

Your own site

<a href="https://agentmods.dev/commands/jaroslavsoucek-art/giovanni/consistency-review"><img src="https://agentmods.dev/badge/commands/jaroslavsoucek-art/giovanni/consistency-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jaroslavsoucek-art/giovanni/consistency-review"><img src="https://agentmods.dev/badge/commands/jaroslavsoucek-art/giovanni/consistency-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,189 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.00040	$0.01189
Opus 5	$0.00020	$0.00594
Sonnet 5	$0.00008	$0.00238
Haiku 4.5	$0.00004	$0.00119

Measured 11d ago against content hash d4f51573e47c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

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

.claude/commands/consistency-review.md · 80 lines

How it starts

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

/consistency-review

Triage the findings of a /consistency-check run, one by one, with the principal as decision-maker. This command is a thin shell — the triage procedure lives in .claude/workflows/consistency-review.md. This file is the invocation contract.

Like /digest, this command routes to a workflow procedure rather than an agent: triage is interactive (per-finding verdicts from the principal), so it runs in the main thread.

Usage

/consistency-review <YYYY-MM-DD>    # triage the report for that date
/consistency-review                 # defaults to the most recent report

Argument syntax

Arg	Type	Default	Meaning
`<YYYY-MM-DD>`	positional date	most recent report	Which report in `memory/audits/consistency/` to triage.

Pre-flight (binding — STOP on failure)

CWD check. Working directory is a Giovanni repo (presence of memory/CLAUDE_MEMORY.md + knowledge/<constitution>.md). Otherwise STOP.
Report file present. memory/audits/consistency/<YYYY-MM-DD>.md exists (after resolving the default). Missing → STOP: ERROR: no consistency report for <YYYY-MM-DD>. Run /consistency-check first.
State file present. memory/audits/consistency/_state.md exists. If missing → seed per the /consistency-check auto-seed rules (shadow window starts today, 28 days) and surface an advisory — a review without a state file can't record precision.
Run entry present. _state.md contains a ## Run <YYYY-MM-DD> entry for the report being reviewed. Missing → STOP with diagnostic (report and state are written together by the agent; a missing entry means a corrupted run).
Not already reviewed. If the run entry has review_status: complete, warn and confirm at prompt (y/N) before re-reviewing — a re-review overwrites the prior verdict counts.

Execution flow

Run pre-flight. STOP on any failure.
Run the workflow procedure per .claude/workflows/consistency-review.md:
- Step 1: open the report, print summary + findings
- Step 2: per-finding interactive triage (accept / reject / defer / false-positive)
- Step 3: apply accepted diffs (bottom-to-top within a file)
- Step 4: update the run entry + aggregate precision metrics in _state.md
- Step 5: propose the batch commit — wait for the principal's explicit go
- Step 6: shadow-mode promotion gate check (only after shadow_mode_end_date)
No auto-commit. The commit in Step 5 happens only on the principal's confirmation.

Read the full file on GitHub · 80 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.

11d ago First seen · 80 lines · 40 tokens per session scan A d4f51573e47c

Subscribe to this mod's changes

consistency-review is a command published in the GitHub repository jaroslavsoucek-art/Giovanni (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,189 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-31.

Claude Code Code review agent-framework agentic-ai ai-agents anthropic chief-of-staff

Giovanni: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/consistency-review

Usage

Argument syntax

Pre-flight (binding — STOP on failure)

Execution flow

What this file has done since we first saw it

Other commands, from other repositories

code-review-swarm

pr-manager

sparc-refinement-optimization-mode

reviewer

code-review

pr-enhance