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/add-debug-logs.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/add-debug-logs)<a href="https://agentmods.dev/commands/liam-hq/liam/add-debug-logs"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/add-debug-logs/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/add-debug-logs"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/add-debug-logs.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.00008 | $0.00093 |
| Opus 5.5 | $0.00003 | $0.00037 |
| Sonnet 5.5 | $0.00002 | $0.00019 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
add-debug-logs 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
Task
Add strategic console.log statements to the specified code to enable debugging. Insert logs at:
- Function entry points with parameter values
- Important variable assignments
- Before and after key operations
- Error catch blocks
- Conditional branches
Use descriptive log messages that include:
- Function/method names
- Variable names and values
- Execution flow indicators
Arguments
$ARGUMENTS
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 · 19 lines · 8 tokens per session scan A ab847ca6dc6a
add-debug-logs is a command published in the GitHub repository liam-hq/liam (5,156 stars, last pushed yesterday), licensed Apache-2.0. It adds 8 tokens to every session and 93 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
context
Triage card for files, modules, or symbols — layer, hotspot, fix history, freshness (relationships, not source bytes).
doctor
Diagnose the Repowise setup — install, API keys, index/store drift — and optionally repair it.
codesage-reset
Fully regenerate a project's CodeSage index under its writer lock, with a separate offline recovery procedure for an unreadable database.
audit-performance
Performance audit. Detects N+1 queries, memory issues, caching gaps, inefficient loops, batch processing problems, algorithm complexity, connection pools, serialization overhead.
pg-health
Read-only PostgreSQL health check with pgbot, then a prioritized diagnosis.
sqlscript-validate
Validates SQLScript code for syntax, patterns, and best practices with auto-fix capability.