A command that shows recent runs managed by Crew, including their status, purpose, start time, and finish time. Crew runs are recorded in the project’s .crew/runs/ folder.

Use it to review all runs or filter for active, completed, or cancelled work, then find runs that may need resuming.

It gives you one view of work that is still running, finished, cancelled, or stuck instead of making you inspect each run folder manually.

list — Command by alphabravo-oss

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/alphabravo-oss/guild/list

Clone the repo

git clone --depth 1 https://github.com/alphabravo-oss/guild

Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 508 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.

Model	Per session	Once invoked
Fable 5	$0.00004	$0.00508
Opus 5	$0.00002	$0.00254
Sonnet 5	$0.00001	$0.00102
Haiku 4.5	$0.00000	$0.00051

Measured 2d ago against content hash a79572463835, 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 2d 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.

plugins/crew/commands/list.md · 57 lines

What it actually says

Crew List

Show recent crew runs from .crew/runs/.

FILTER="$ARGUMENTS"

Default filter: show all runs, most recent first.

--active → only status in {initialized, scouting, plan_approval, executing, dual_verification}
--completed → only status == "completed"
--all → everything including cancelled

Behavior

List .crew/runs/ if it exists. If not, tell the user "No crew runs in this project yet."
For each run dir, read state.json and extract:
- run_id
- intent (truncate to 80 chars)
- status
- phase
- created_at
- completed_at (if present)
Render a table in chat:

| run id | status | intent | started | finished |
|---|---|---|---|---|
| crew-20260512-143218-a3f9 | ✓ completed | deploy Shiro to Azure on RHEL | 14:32:18 | 15:47:02 |
| crew-20260512-131045-7c1e | ⚠ stuck | get the airgap bundle pulling all… | 13:10:45 | — |
| crew-20260512-094500-2bd1 | ↻ executing | rotate the prod DB creds and upd… | 09:45:00 | — |

Status icons:

✓ completed
↻ in-progress (any active phase)
⚠ stuck
✗ cancelled
— failed / unknown

If there are active runs, remind the user they can resume with /crew:resume <run-id>.

Rules

Read-only. Never modify state.json or run artifacts.
Sort by created_at descending (newest first).
If a state.json is malformed or unreadable, render the row with status: ✗ unreadable rather than failing the whole list.

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.

2d ago First seen · 57 lines · 4 tokens per session scan A a79572463835

Subscribe to this mod's changes

list is a command published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 2d ago), licensed MIT. It adds 4 tokens to every session and 508 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-31.

Project management

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

speckit.auto

Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.

VisActor/VChart · 31 tokens

daily-priorities

Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).

DIGI-UW/OpenELIS-Global-2 · 0 tokens

list