list

A set of commands for viewing and inspecting work threads stored in a project folder. It groups threads by status and can show the current milestone, focus, and next steps.

In plain words
What is it for?
Use it to list all threads, check the active thread, or open a detailed view of a specific thread and its progress.
Why use it?
It gives you one place to see which pieces of work are active, finished, blocked, or abandoned, without opening each thread file manually.

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/paulonasc/orchestra/list
Clone the repo
git clone --depth 1 https://github.com/paulonasc/orchestra
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 617 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.00000 $0.00617
Opus 5 $0.00000 $0.00309
Sonnet 5 $0.00000 $0.00123
Haiku 4.5 $0.00000 $0.00062

Measured 3d ago against content hash 0080fd6dc011, 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 3d 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.

commands/list.md · 61 lines

How it starts

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

/o list / active / plan / thread — View state

/o list — List all threads

Scan threads/ and render a summary table grouped by status. Read the status field from each thread's progress.yaml (default: active if missing).

## Active threads

001  honestclaw-mvp       M0 87% | M1 0%    3 repos
003  mobile-app           M0 20%             2 repos    ⚠ blocked

## Completed

002  payment-integration  M0 100% | M1 100%  1 repo     completed 2026-03-15

## Abandoned

004  old-auth-spike       M0 30%             1 repo     abandoned 2026-03-10

Active threads first (these are what matter). Completed threads show their completed_at date. Abandoned threads show date and are dimmed. If a category is empty, omit it.

/o active — What are we working on?

Read state/active-thread.md and state/sessions/{session-id}.md. Show:

## Active

Thread: 001-honestclaw-mvp
Milestone: M0 — Scaffolding & CI/CD (87%)
Current focus: Building GitHub Actions CI/CD pipelines for API and frontend
Next steps: M0.27 API CI/CD, M0.28 Frontend CI/CD

If the session file exists and is recent, include the key context and current state from it.

/o — Thread deep dive

Read the thread's spec.md, plan.md, verification.md, conversation.md, and related handoffs/. Render:

  1. Spec summary — problem, approach, acceptance criteria
  2. Plan — current phase, milestone progress, open questions (from plan.md)
  3. Risks — from ## Risks in spec
  4. Alternatives considered — from ## Alternatives in spec (what was rejected and why)
  5. Verification status — automated and manual test results
  6. Progress — milestone items for this thread with status
  7. Handoffs — recent handoffs related to this thread
  8. Decisions — decisions tagged with this thread

/o plan — Show thread plan

Read the plan for the active thread (or specify a thread: /o plan 001-slug).

  1. Read state/active-thread.md to find the current thread (unless thread specified)
  2. Read threads/NNN-slug/plan.md
  3. Render: objective, current phase, items with status, open questions, dependencies

Read the full file on GitHub · 61 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. 3d ago First seen · 61 lines · 0 tokens per session scan A 0080fd6dc011

Subscribe to this mod's changes

list is a command published in the GitHub repository paulonasc/orchestra (15 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 617 tokens. 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.