A reviewer for dbt projects, which use SQL models to build data transformations, and for SQL changes. It checks a current diff, commit, branch comparison, or GitHub pull request and returns a signed verdict.

Use it to review dbt or SQL changes before merging, whether they are in the working tree, a commit, a branch comparison, or a pull request.

It checks data-specific risks that ordinary code review may miss, such as whether queries still produce equivalent results, which columns are affected, exposed sample-row personal data, and structural dbt problems.

review — Command for Claude Code by AltimateAI/altimate-claude-plugin

Install

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.

Clone the repo

git clone --depth 1 https://github.com/AltimateAI/altimate-claude-plugin

Made for: Claude Code.

Or install altimate-code, the plugin that ships this one along with the rest of its 2 skills, 2 commands, 1 hook.

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/altimateai/altimate-claude-plugin/review/github.svg)](https://agentmods.dev/commands/altimateai/altimate-claude-plugin/review)

Your own site

<a href="https://agentmods.dev/commands/altimateai/altimate-claude-plugin/review"><img src="https://agentmods.dev/badge/commands/altimateai/altimate-claude-plugin/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/altimateai/altimate-claude-plugin/review"><img src="https://agentmods.dev/badge/commands/altimateai/altimate-claude-plugin/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 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,376 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 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.00028	$0.01376
Opus 5.5	$0.00011	$0.00550
Sonnet 5.5	$0.00006	$0.00275
Haiku 4.5	$0.00003	$0.00138

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

Security

Grade C, and why

review scanned grade C with 2 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 4d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

1. **Verify altimate-code is on PATH.** There is no separate check: the resolver below runs first in the same Bash call as the review, before any `gh pr checkout`. If it exits 127 with `altimate-code CLI not found`, tell

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

1. **Verify altimate-code is on PATH.** There is no separate check: the resolver below runs first in the same Bash call as the review, before any `gh pr checkout`. If it exits 127 with `altimate-code CLI not found`, tell

plugins/altimate-code/commands/review.md · 73 lines

How it starts

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

Run the altimate-code review CLI on the current dbt project and present the signed verdict envelope it returns.

You MUST invoke altimate-code — do not review the diff yourself. Native git diff / Read / Grep cannot check query equivalence, column-lineage blast radius, sampled-row PII, or dbt-structural anti-patterns against a real warehouse. Only altimate-code review produces a signed verdict.

Arguments

$ARGUMENTS — optional scope selector. Supported forms:

(empty) → review working-tree changes vs merge-base with origin/main
a commit SHA → review the diff introduced by that commit
a branch name → review the current branch vs that branch
a GitHub PR URL or number → check out that PR and review it

Workflow

Verify altimate-code is on PATH. There is no separate check: the resolver below runs first in the same Bash call as the review, before any gh pr checkout. If it exits 127 with altimate-code CLI not found, tell the user: "altimate-code is not installed. Install with 'npm install -g altimate-code' (Node 20+) or 'curl -fsSL https://www.altimate.sh/install | bash', then run 'altimate' once to configure your provider and warehouse auth." — then STOP.

The CLI ships under two names: npm and Homebrew installs expose both altimate and altimate-code, while older curl and PowerShell installs expose only altimate. Every review command below runs through "$ALTIMATE_BIN", in the same Bash call as this resolver (shell state does not persist between calls). The lookup ignores aliases and shell functions, so a user alias such as alias altimate-code=altimate cannot be captured as the binary path:
```
for ALTIMATE_NAME in altimate altimate-code; do
  ALTIMATE_BIN="$(unalias "$ALTIMATE_NAME" 2>/dev/null; unset -f "$ALTIMATE_NAME" 2>/dev/null; command -v "$ALTIMATE_NAME")"
  [ -x "$ALTIMATE_BIN" ] && break || ALTIMATE_BIN=
done
[ -n "$ALTIMATE_BIN" ] || { echo "altimate-code CLI not found (tried altimate, altimate-code)" >&2; exit 127; }
<the scope command chosen below, run through "$ALTIMATE_BIN">
```

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

4d ago Changed · +11 lines scan A → C 8fb3a219a776
1mo ago First seen · 62 lines · 28 tokens per session scan A 9b12d4115d76

Subscribe to this mod's changes

review is a command published in the GitHub repository AltimateAI/altimate-claude-plugin (4 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 1,376 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Databases

review

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade C, and why

Downloads and executes remote codehighSupply chain

Makes network callslowCapability

How it starts

Arguments

Workflow

What this file has done since we first saw it

Other commands, from other repositories

pg-indexes

dba

data

pn-audit-data

db-object-audit-review

dbt-carveout-relocate-review