Borrowing it
Nothing to install: this file belongs to NguyenSiTrung/Conductor-Beads. 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/NguyenSiTrung/Conductor-Beads/main/.claude/skills/beads/commands/list.mdgit clone --depth 1 https://github.com/NguyenSiTrung/Conductor-BeadsWrote 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/nguyensitrung/conductor-beads/list)<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/list"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/list/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/nguyensitrung/conductor-beads/list"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/list.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.00000 | $0.00704 |
| Opus 5 | $0.00000 | $0.00352 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00070 |
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 9d 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.
This is a copy
100% identical to list — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 issuesbd list --type bug --assignee alice: Alice's assigned bugsbd list --label backend,needs-review: Backend issues needing reviewbd list --title "auth": Issues with "auth" in the title
Advanced Usage
bd list --title-contains "auth" --status open: Search open issues for auth-related workbd list --priority-min 0 --priority-max 1: Critical and high priority issues onlybd list --created-after 2025-01-01 --status open: Recent open issuesbd list --empty-description --status open: Open issues missing descriptionsbd list --no-assignee --priority 1: High priority unassigned workbd list --desc-contains "TODO" --notes-contains "review": Find items needing attention
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.
- 9d ago First seen · 65 lines · 0 tokens per session scan A a986fdc0400c
list is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 704 tokens. A static security scan graded it A with 0 findings. It is 100% identical to list, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.