Borrowing it
Nothing to install: this file belongs to Traves-Theberge/Orchestra. 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/Traves-Theberge/Orchestra/main/.codex/skills/orchestra-cli/SKILL.mdgit clone --depth 1 https://github.com/Traves-Theberge/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/skills/traves-theberge/orchestra/orchestra-cli)<a href="https://agentmods.dev/skills/traves-theberge/orchestra/orchestra-cli"><img src="https://agentmods.dev/badge/skills/traves-theberge/orchestra/orchestra-cli/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/skills/traves-theberge/orchestra/orchestra-cli"><img src="https://agentmods.dev/badge/skills/traves-theberge/orchestra/orchestra-cli.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.00061 | $0.04577 |
| Opus 5.5 | $0.00024 | $0.01831 |
| Sonnet 5.5 | $0.00012 | $0.00915 |
| Haiku 4.5 | $0.00006 | $0.00458 |
Grade A, and why
orchestra-cli scanned grade A with 1 finding 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 15d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Task metadata update, explicit dispatch/retry/stop, project import, worktree create/remove, terminal send/wait and PR publication/merge remain unavailable CLI commands. “Pause” must not map to destructive legacy stop/res How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestra CLI
Use Orchestra's backend as the authority for projects, tasks and execution observations. Keep Kanban task identity separate from its repository, worktree, agent session and PR.
Resolve the CLI and backend
Use an explicitly supplied executable or ORCHESTRA_CLI_COMMAND when present. Otherwise resolve orchestra on PATH. In an Orchestra checkout, the staged build is apps/backend/dist/orchestra/orchestra.exe on Windows or apps/backend/dist/orchestra/orchestra elsewhere. If no binary exists, report that or build the repository CLI when development is authorized. Do not substitute orca or orchestrad; they are different interfaces. Invoke a chosen executable directly with argument arrays, not shell evaluation of a command string.
Read the chosen binary's --help, then the relevant command's --help. Use only commands it advertises. Older binaries may have only start, check and check-pr-body; absence of observation commands means that build needs updating. Never invent a future command or assume the installed binary matches this skill.
Observation commands use --base-url or ORCHESTRA_BASE_URL, and ORCHESTRA_API_TOKEN in the environment. Choose the backend/profile the user is operating; do not probe unrelated servers or assume cwd identifies a remote project. Avoid tokens in command arguments, logs or final responses. A 401/403 is not an empty project/task list. Audit managed-backend credentials can change on relaunch; refresh the selected profile credential without printing it. Never change provider account settings to connect the CLI.
The CLI does not select desktop profiles automatically. For this repository's explicitly selected Windows audit-dev instance, desktop connection profiles are in %LOCALAPPDATA%\Orchestra\audit-dev\desktop\backend-profiles.json: select the entry matching activeProfileId, then assign its baseUrl and apiToken to the process environment without displaying the file or token. Other instances use their own configured user-data directory; do not assume this audit path describes them. If connection context is unavailable, request it rather than guessing. Restore temporary environment assignments after inspection.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 15d ago Changed · +22 lines ebf30df5b2cb
- 19d ago Changed · +49 lines · +17 tokens per session cd21c0b8ba4d
- 20d ago First seen · 76 lines · 44 tokens per session scan A 9e7f5f8a41a2
orchestra-cli is a skill published in the GitHub repository Traves-Theberge/Orchestra (26 stars, last pushed 10d ago), licensed Apache-2.0. It adds 61 tokens to every session and 4,577 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-05.
Other skills, from other repositories
agtx-oneshot
One-shot a whole project on an agtx board: decompose the goal, run every task unattended, unblock the workers, and merge each one. Use when the user wants a long autonomous run rather than a single session.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
symphony-skill
Single Symphony operator router for Kanban tickets, service/TUI runs, WORKFLOW.md and prompt config, lane customization, delegation, production-ready app delivery planning, OneShot runs, repo and monorepo bootstrap, and worker failure triage.
kagan
Read a ticket, link threads, and move work through the native Kagan board when the user asks for ticket work.
superpm
Produce focused PM artifacts and verify them with a critic. Use for PRDs, strategy, OKRs, roadmaps, specs, research, analytics, GTM, growth, pricing, positioning, market signals, release notes, retros, and resume reviews.
Mochi-a-pm
Use this skill when the user or another AI needs project management, task tracking, priority assignment, timeline planning, or progress review. Mochi is a cute but deadly serious project manager AI.