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/commands/conductor-status.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/conductor-status)<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/conductor-status"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-status/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/conductor-status"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-status.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.00006 | $0.01336 |
| Opus 5 | $0.00003 | $0.00668 |
| Sonnet 5 | $0.00001 | $0.00267 |
| Haiku 4.5 | $0.00001 | $0.00134 |
Grade A, and why
conductor-status 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- status — 95% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor Status
Show the current status of this Conductor project.
1. Check Setup
If conductor/tracks.md doesn't exist, tell user to run /conductor-setup first.
2. Read State
- Read
conductor/tracks.md - List all track directories:
conductor/tracks/*/ - Read each
conductor/tracks/<track_id>/plan.md
3. Calculate Progress
For each track:
- Read
metadata.jsonto get priority and depends_on - Count total tasks (lines with
- [ ],- [~],- [x]) - Count completed
[x] - Count in-progress
[~] - Count pending
[ ] - Calculate percentage: (completed / total) * 100
- Check if blocked (has incomplete dependencies)
4. Present Summary
Format the output like this:
## Conductor Status
**Active Track:** [track name] ([completed]/[total] tasks - [percent]%)
**Overall Status:** In Progress | Complete | No Active Tracks
### Priority Grouping
Group tracks by priority (read from metadata.json):
- 🔴 Critical
- 🟠 High
- 🟡 Medium
- 🟢 Low
### Tracks by Priority
**🔴 Critical**
- [~] auth_20241215 - User Authentication (30%)
**🟠 High**
- [ ] payments_20241216 - Payment Integration 🔒
⤷ Depends on: auth_20241215
**🟡 Medium**
- [x] setup_20241214 - Project Setup (100%)
**🟢 Low**
- [ ] docs_20241217 - Documentation
### Blocked Tracks
Show 🔒 for tracks with incomplete dependencies.
Show dependency chain: "Depends on: [track_ids]"
### Blockers
List all tasks marked with `[!]`:
- Task name (track_id): Reason
### Current Task
[The task marked with [~] in the active track's plan.md]
### Next Action
[The next task marked with [ ] in the active track's plan.md]
### Recent Completions
[Last 3 tasks marked [x] with their commit SHAs]
5a. Parallel Execution Status
If any track has parallel_state.json:
### Parallel Execution (Phase: [phase_name])
**Status:** Running | Waiting for workers | Complete
**Workers:**
- 🟢 worker_1_auth: Completed (commit: abc1234)
- 🔵 worker_2_config: In Progress (45 min)
- ⚪ worker_3_utils: Pending (depends on worker_1)
**File Locks:**
- src/auth/index.ts → worker_1_auth
- src/config/index.ts → worker_2_config
**Progress:** 1/3 workers complete
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.
- 10d ago First seen · 183 lines · 6 tokens per session scan A 5d95152aea27
conductor-status is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 1,336 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-30.
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.