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/create-plan.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/create-plan)<a href="https://agentmods.dev/commands/liam-hq/liam/create-plan"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/create-plan/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/create-plan"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/create-plan.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.00011 | $0.00428 |
| Opus 5.5 | $0.00004 | $0.00171 |
| Sonnet 5.5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
create-plan 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
Create a comprehensive PLANS.md file in the project root directory to track project execution.
Input Handling
If the arguments contain a GitHub issue reference:
- Extract the issue number from arguments (format:
#123,123, or GitHub URL) - Use
gh issue view <issue-number>to fetch the issue details - Understand the requirements and context from the issue
- Search the codebase for relevant files if needed
- Use the issue information to populate the PLANS.md sections
Structure
The PLANS.md should include these sections:
-
Purpose / Big Picture
- Project goal summary
- User benefits
- Expected user-visible behavior
-
Initial Requirements & Scope
- High-level requirements
- Key features list
- In-scope vs. out-of-scope items
-
Milestones & Deliverables
- Work phases breakdown
- Specific deliverables
- Acceptance criteria
-
Progress
- Checkbox task list for granular tracking
- Completion status
- Progress dates
-
Surprises & Discoveries
- Unexpected learnings
- Technical challenges
- New insights
-
Decision Log
- Key decisions with dates
- Reasoning and context
- Supporting references
-
Outcomes & Retrospectives
- Milestone results
- Lessons learned
- What went well / could improve
Guidelines
- Start with information gathered from the current project context
- Use the user's input to understand the project scope
- Keep it concise but comprehensive
- Format as a living document that can evolve
- Use markdown checkboxes
- [ ]for trackable tasks
Arguments
Accepts:
- Project description or context (free text)
- GitHub issue number (e.g.,
123or#123) - GitHub issue URL
$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 · 79 lines · 11 tokens per session scan A 15d7f4a9ed60
create-plan is a command published in the GitHub repository liam-hq/liam (5,156 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 428 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
complete
Review implementation evidence and plan the spec completion transaction.
member-import
Bulk member import from CSV/Excel with validation, batch processing, and error handling.
brief
Load current spec intent and lifecycle before creating a new specification.
prd-sync
Converte PDFs de PRD soltos em prds/ para markdown versionado e roda o review (principal-engineer + prd-review).
export
The livewiki export command turns the project's curated wiki into a deliverable artifact on disk: either a flattened snapshot under .livewiki/export/ / (for generic, github-wiki, and gitlab-wiki targets) or a synthesized repository-root README.md (for the readme target).
report
📝 Report Router — Multi-purpose reporting (create report, update docs, or generate from template).