Liam ERD is a tool that turns database schemas into interactive entity-relationship diagrams, visual maps showing tables and their relationships. It helps people understand and document database structures, including complex schemas.
Borrowing it
Nothing to install: this file belongs to liam-hq/liam. 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/liam-hq/liam/main/.claude/commands/review.mdgit clone --depth 1 https://github.com/liam-hq/liamWrote 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/liam-hq/liam/review)<a href="https://agentmods.dev/commands/liam-hq/liam/review"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/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/liam-hq/liam/review"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/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.00012 | $0.00190 |
| Opus 5.5 | $0.00005 | $0.00076 |
| Sonnet 5.5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
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 2mo 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
CodeRabbit CLI Review (Local changes only)
Do NOT check or review pull requests. Do NOT call gh commands.
Run CodeRabbit locally against the working repository only.
Run
Execute exactly:
coderabbit --plain -t all --base origin/main -c claude.md coderabbit.yaml
Parse → Tasks
From the output, extract for each finding:
- Severity: Critical | Warning | Info
- File and line
- Description
- Suggested fix
Create one TodoWrite per finding:
title:[Severity] <file>:<line> <short description>body:<Suggested fix>metadata:{ "file": "<file>", "line": <line>, "severity": "<Severity>" }
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.
- 2mo ago First seen · 33 lines · 12 tokens per session scan A aa361e4d6663
review is a command published in the GitHub repository liam-hq/liam (5,156 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 190 once invoked, about $0.0000 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
pg-indexes
Review unused indexes that are safe to drop (pgbot).
dba
Invoke the Database Administrator for schema design, indexing, query tuning, safe migrations, replication, and backups (Postgres/MySQL OLTP).
data
Invoke the Data Engineer for ETL/ELT, dbt, warehouses, streaming, orchestration, and data quality.
harness-review
Review the current change set from an opposing harness-engineering perspective.
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.
baseline
This page documents the CLI implementation for baseline lifecycle operations, covering subcommand registration, error-safe execution, and human-readable reporting.