list

Issue-listing commands with filters for status, priority, type, assignee, labels, text, and dates. They return only the work items matching the conditions you choose.

In plain words
What is it for?
Find open, blocked, high-priority, assigned, labelled, recently changed, or text-matching issues, with limits on the number of results.
Why use it?
They reduce the effort of finding the relevant tasks in a busy project and support focused views of current work.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/gastownhall/beads/list
Clone the repo
git clone --depth 1 https://github.com/gastownhall/beads
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 704 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00005 $0.00704
Opus 5 $0.00003 $0.00352
Sonnet 5 $0.00001 $0.00141
Haiku 4.5 $0.00001 $0.00070

Measured yesterday against content hash 990a0e6ef5af, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

list 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • list — 100% identical, 2 lines differ
plugins/beads/skills/beads/commands/list.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

List beads issues with optional filtering.

Basic Filters

  • --status, -s: Filter by status (open, in_progress, blocked, closed)
  • --priority, -p: Filter by priority (0-4: 0=critical, 1=high, 2=medium, 3=low, 4=backlog)
  • --type, -t: Filter by type (bug, feature, task, epic, chore, decision)
  • --assignee, -a: Filter by assignee
  • --label, -l: Filter by labels (comma-separated, must have ALL labels)
  • --label-any: Filter by labels (OR semantics, must have AT LEAST ONE)
  • --title: Filter by title text (case-insensitive substring match)
  • --limit, -n: Limit number of results

Advanced Filters

Pattern Matching

  • --title-contains: Search for text in title (case-insensitive)
  • --desc-contains: Search for text in description (case-insensitive)
  • --notes-contains: Search for text in notes (case-insensitive)

Date Ranges

  • --created-after: Issues created after date (YYYY-MM-DD or ISO 8601)
  • --created-before: Issues created before date
  • --updated-after: Issues updated after date
  • --updated-before: Issues updated before date
  • --closed-after: Issues closed after date
  • --closed-before: Issues closed before date

Priority Range

  • --priority-min: Minimum priority (inclusive)
  • --priority-max: Maximum priority (inclusive)

Empty/Null Checks

  • --empty-description: Find issues with no description
  • --no-assignee: Find unassigned issues
  • --no-labels: Find issues with no labels

Examples

Basic Usage

  • bd list --status open --priority 1: High priority open issues
  • bd list --type bug --assignee alice: Alice's assigned bugs
  • bd list --label backend,needs-review: Backend issues needing review
  • bd list --title "auth": Issues with "auth" in the title

Advanced Usage

  • bd list --title-contains "auth" --status open: Search open issues for auth-related work
  • bd list --priority-min 0 --priority-max 1: Critical and high priority issues only
  • bd list --created-after 2025-01-01 --status open: Recent open issues
  • bd list --empty-description --status open: Open issues missing descriptions
  • bd list --no-assignee --priority 1: High priority unassigned work
  • bd list --desc-contains "TODO" --notes-contains "review": Find items needing attention

Read the full file on GitHub · 65 lines

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. yesterday First seen · 65 lines · 5 tokens per session scan A 990a0e6ef5af

Subscribe to this mod's changes

list is a command published in the GitHub repository gastownhall/beads (26,754 stars, last pushed yesterday), licensed MIT. It adds 5 tokens to every session and 704 once invoked, about $0.0000 per session on Opus 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.