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-issue.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-issue)<a href="https://agentmods.dev/commands/liam-hq/liam/create-issue"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/create-issue/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-issue"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/create-issue.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.00007 | $0.00404 |
| Opus 5.5 | $0.00003 | $0.00162 |
| Sonnet 5.5 | $0.00001 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
create-issue 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 new issue in a GitHub repository using the GitHub CLI.
Process
- Analyze the request: First, understand the context and technical implications
- Gather information: If the issue involves technical implementation, think through:
- Current state vs desired state
- Technical requirements and dependencies
- Potential implementation approaches
- Impact and risks
- Structure the issue: Create a well-structured issue with:
- Clear title
- Detailed body with background, requirements, and technical considerations
- Use proper markdown formatting
Arguments
$ARGUMENTS
Argument Handling:
- When arguments are provided: Create an issue based on the given content
- When arguments are empty: Detect technical discussions from recent conversation and suggest creating an issue based on that context
- When instructed to "create from conversation": Analyze conversation history to generate an issue
Best Practices
- Argument validation: When arguments are empty, first analyze available conversation context
- Conversation history utilization: Auto-detect technical investigations, bug discoveries, refactoring proposals
- Research integration: Use code investigation and search results as evidence for the issue
- Structured issues: Include the following sections:
- Overview (problem summary)
- Current state (technical current situation)
- Investigation results (detailed research findings)
- Action items (specific work to be done)
- Impact analysis (risks and benefits)
- Technical considerations (implementation notes)
- Evidence documentation: Include specific file paths, line numbers, and search results
- Cross-repository references: When referencing PRs or issues from repositories other than the target repository, use the full format
repository#number(e.g.,liam-hq/liam#2991) instead of just#numberto ensure proper GitHub linking
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 · 40 lines · 7 tokens per session scan A ad832ecc6b11
create-issue is a command published in the GitHub repository liam-hq/liam (5,156 stars, last pushed yesterday), licensed Apache-2.0. It adds 7 tokens to every session and 404 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
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
spec-forge
Use when generating software specifications — full chain ([Idea]→[Decompose]→[PRD]→SRS→Tech Design→Review) or individual documents.
new-migration
Scaffold a new database migration file pair (up + down) with auto-detection of migration tool and numbering.
harness-adopt
Apply Harness Starter Kit to the current target repository with the prompt-first adoption workflow.
tdd-feature
Implement a new feature using full TDD loop.
adr-supersede
Create a new ADR that supersedes an existing one.