liam: Command for Claude Code

.claude/commands/read-issue.md

read-issue is a command for Claude Code from liam-hq/liam. It costs 10 tokens per session (144 once invoked), scanned A, original, Apache-2.0.

A command for retrieving a GitHub issue, which is a tracked bug, request, or task, and presenting it with related code context.

In plain words
What is it for?
Use it with an issue number to understand the reported problem and locate the code that may need attention.
Why use it?
It gathers the issue details and relevant files in one place instead of requiring separate manual searches.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is liam-hq/liam's own configuration. It tells Claude Code how to work on liam itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything liam configures →

About the project

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.

liam-hq/liam · 5,156 stars · on GitHub · liambx.com

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/liam-hq/liam/main/.claude/commands/read-issue.md
Clone the repo
git clone --depth 1 https://github.com/liam-hq/liam

Made for: Claude Code.

Wrote 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.

agentmods badge for read-issue

README.md
[![agentmods](https://agentmods.dev/badge/commands/liam-hq/liam/read-issue/github.svg)](https://agentmods.dev/commands/liam-hq/liam/read-issue)
Your own site
<a href="https://agentmods.dev/commands/liam-hq/liam/read-issue"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/read-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.

agentmods 80×15 button for read-issue

Your own site · 80×15
<a href="https://agentmods.dev/commands/liam-hq/liam/read-issue"><img src="https://agentmods.dev/badge/commands/liam-hq/liam/read-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 144 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00144
Opus 5.5 $0.00004 $0.00058
Sonnet 5.5 $0.00002 $0.00029
Haiku 4.5 $0.00001 $0.00014

Measured 2mo ago against content hash 19d46d628add, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

read-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.

.claude/commands/read-issue.md · 18 lines

What it actually says

Task

Use the gh command to fetch the GitHub issue specified in the arguments and present its contents for analysis.

Steps

  1. Extract the issue number from the arguments (format: #123 or just 123)
  2. Use gh issue view <issue-number> to fetch the issue details
  3. Understand the problem described in the issue
  4. Search the codebase for relevant files related to the issue
  5. Present the issue information and relevant code context in a clear, readable format

Arguments

The command accepts an issue number (e.g., 123 or #123)

Changes

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.

  1. 2mo ago First seen · 18 lines · 10 tokens per session scan A 19d46d628add

Subscribe to this mod's changes

read-issue is a command published in the GitHub repository liam-hq/liam (5,156 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 144 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.