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/commit.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/commit)<a href="https://agentmods.dev/commands/liam-hq/liam/commit"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/commit/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/commit"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/commit.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.00000 | $0.00931 |
| Opus 5.5 | $0.00000 | $0.00372 |
| Sonnet 5.5 | $0.00000 | $0.00186 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
commit 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Let's commit the changes.
Split large changes: If changes touch multiple concerns, split them into separate commits Write a commit message that matches the content of your change: Clearly describe what was changed in this commit. A good commit message should:
- Specify the component or feature affected (e.g., "authentication module").
- Describe the action taken (e.g., "fixed a bug," "added a new feature").
- Avoid vague messages like "fix bug" or "update code."
Examples of good commit messages:
- 🐛 Fixed a bug in the authentication module causing login failures
- ✨ Added a new feature to filter tables by column
- 📝 Updated README.md with new installation instructions
Examples of bad commit messages:
- "fix bug"
- "update code"
- "changes made"
- Use gitmoji (optional, recommended): Write commit messages using the emoji (e.g., ✨) itself, not the textual representation (e.g.,
:sparkles:)
Examples
- ✨ Added a new feature to filter tables
- 🐛 Fixed a typo in the welcome message
- 📝 Updated README.md with new installation instructions
Gitmoji Reference
Frequently Used
- 🚸
:children_crossing:- Improve user experience / usability - ✨
:sparkles:- Introduce new features - 🐛
:bug:- Fix a bug - ♻️
:recycle:- Refactor code - ⚡
:zap:- Improve performance - 💄
:lipstick:- Add or update the UI and style files - 🎨
:art:- Improve structure / format of the code - 📝
:memo:- Add or update documentation - 🔧
:wrench:- Add or update configuration files
Testing & Quality
- ✅
:white_check_mark:- Add, update, or pass tests - 🚨
:rotating_light:- Fix compiler / linter warnings - 🧪
:test_tube:- Add a failing test - 🥅
:goal_net:- Catch errors
Critical Changes
- 🚑
:ambulance:- Critical hotfix - 💥
:boom:- Introduce breaking changes - 🔒
:lock:- Fix security or privacy issues
Dependencies & CI/CD
- ➕
:heavy_plus_sign:- Add a dependency - ➖
:heavy_minus_sign:- Remove a dependency - ⬆️
:arrow_up:- Upgrade dependencies - ⬇️
:arrow_down:- Downgrade dependencies - 💚
:green_heart:- Fix CI Build - 👷
:construction_worker:- Add or update CI build system
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 · 88 lines · 0 tokens per session scan A 3de8a45e59f6
commit is a command published in the GitHub repository liam-hq/liam (5,156 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 931 tokens. 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
implement-feature
Implement an approved feature plan with benefit-based placement, TDD, revision-bound evidence, and PR-ready output.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.
complete
Review implementation evidence and plan the spec completion transaction.
verify
Run verification commands and confirm output before making success claims. Use before committing, creating PRs, or claiming work is complete. Evidence before assertions, ALWAYS.
autotask
Execute development task autonomously from description to PR-ready - handles implementation, testing, and git workflow without supervision.
mmt
Run the mutation-minded testing workflow — architecture review, test judgement, weak-test rewrite, mutation-resistant branch closure — on a file, directory, or diff.