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.
git clone --depth 1 https://github.com/paulonasc/orchestraWrote 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/paulonasc/orchestra/list)<a href="https://agentmods.dev/commands/paulonasc/orchestra/list"><img src="https://agentmods.dev/badge/commands/paulonasc/orchestra/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/paulonasc/orchestra/list"><img src="https://agentmods.dev/badge/commands/paulonasc/orchestra/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.00617 |
| Opus 5.5 | $0.00000 | $0.00247 |
| Sonnet 5.5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
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 1mo 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.
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:
- Spec summary — problem, approach, acceptance criteria
- Plan — current phase, milestone progress, open questions (from
plan.md) - Risks — from
## Risksin spec - Alternatives considered — from
## Alternativesin spec (what was rejected and why) - Verification status — automated and manual test results
- Progress — milestone items for this thread with status
- Handoffs — recent handoffs related to this thread
- 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).
- Read
state/active-thread.mdto find the current thread (unless thread specified) - Read
threads/NNN-slug/plan.md - Render: objective, current phase, items with status, open questions, dependencies
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.
- 1mo ago First seen · 61 lines · 0 tokens per session scan A 0080fd6dc011
list is a command published in the GitHub repository paulonasc/orchestra (15 stars, last pushed 6mo 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
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.