Borrowing it
Nothing to install: this file belongs to Jonkimi/create-conductor-flow. 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/Jonkimi/create-conductor-flow/main/.claude/commands/conductor-status.mdgit clone --depth 1 https://github.com/Jonkimi/create-conductor-flowWrote 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/jonkimi/create-conductor-flow/conductor-status)<a href="https://agentmods.dev/commands/jonkimi/create-conductor-flow/conductor-status"><img src="https://agentmods.dev/badge/commands/jonkimi/create-conductor-flow/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/jonkimi/create-conductor-flow/conductor-status"><img src="https://agentmods.dev/badge/commands/jonkimi/create-conductor-flow/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.00007 | $0.00728 |
| Opus 5.5 | $0.00003 | $0.00291 |
| Sonnet 5.5 | $0.00001 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
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 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1.0 SYSTEM DIRECTIVE
You are an AI agent. Your primary function is to provide a status overview of the current tracks file. This involves reading the Tracks Registry file, parsing its content, and summarizing the progress of tasks.
CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.
1.1 SETUP CHECK
PROTOCOL: Verify that the Conductor environment is properly set up.
-
Verify Core Context: Using the Universal File Resolution Protocol, resolve and verify the existence of:
- Tracks Registry
- Product Definition
- Tech Stack
- Workflow
-
Handle Failure:
- If ANY of these files are missing, you MUST halt the operation immediately.
- Announce: "Conductor is not set up. Please run
/conductor-setupto set up the environment." - Do NOT proceed to Status Overview Protocol.
2.0 STATUS OVERVIEW PROTOCOL
PROTOCOL: Follow this sequence to provide a status overview.
2.1 Read Project Plan
- Locate and Read: Read the content of the Tracks Registry (resolved via Universal File Resolution Protocol).
- Locate and Read Tracks:
- Parse the Tracks Registry to identify all registered tracks and their paths.
- Parsing Logic: When reading the Tracks Registry to identify tracks, look for lines matching either the new standard format
- [ ] **Track:or the legacy format## [ ] Track:.
- Parsing Logic: When reading the Tracks Registry to identify tracks, look for lines matching either the new standard format
- For each track, resolve and read its Implementation Plan (using Universal File Resolution Protocol via the track's index file).
- Parse the Tracks Registry to identify all registered tracks and their paths.
2.2 Parse and Summarize Plan
- Parse Content:
- Identify major project phases/sections (e.g., top-level markdown headings).
- Identify individual tasks and their current status (e.g., bullet points under headings, looking for keywords like "COMPLETED", "IN PROGRESS", "PENDING").
- Generate Summary: Create a concise summary of the project's overall progress. This should include:
- The total number of major phases.
- The total number of tasks.
- The number of tasks completed, in progress, and pending.
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 · 58 lines · 7 tokens per session scan A 154e05b991a8
conductor-status is a command published in the GitHub repository Jonkimi/create-conductor-flow (5 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 728 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
feature
Create a new feature via SDLC-based multi-agent collaboration.
flow-archive
Run the canonical flow/archive Flow lifecycle.
flow-cleanup
Run the canonical flow/cleanup Flow lifecycle.
flow-sync
Run the canonical flow/sync Flow lifecycle.
codex-mvp-split
A command that helps choose the smallest first version of a large feature. MVP means minimum viable product: the smallest version that delivers useful value and can be expanded later.
pod
Create a Wakeflow pod for parallel work, or close one after its branch has been merged or abandoned.