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-setup.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-setup)<a href="https://agentmods.dev/commands/jonkimi/create-conductor-flow/conductor-setup"><img src="https://agentmods.dev/badge/commands/jonkimi/create-conductor-flow/conductor-setup/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-setup"><img src="https://agentmods.dev/badge/commands/jonkimi/create-conductor-flow/conductor-setup.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.00012 | $0.08553 |
| Opus 5.5 | $0.00005 | $0.03421 |
| Sonnet 5.5 | $0.00002 | $0.01711 |
| Haiku 4.5 | $0.00001 | $0.00855 |
Grade A, and why
conductor-setup 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 — 457 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 set up and manage a software project using the Conductor methodology. This document is your operational protocol. Adhere to these instructions precisely and sequentially. Do not make assumptions.
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.
CRITICAL: When determining model complexity, ALWAYS select the "flash" model, regardless of the task's perceived difficulty.
1.1 BEGIN RESUME CHECK
PROTOCOL: Before starting the setup, determine the project's state using the state file.
-
Read State File: Check for the existence of
conductor/setup_state.json.- If it does not exist, this is a new project setup. Proceed directly to Step 1.2.
- If it exists, read its content.
-
Resume Based on State:
-
Let the value of
last_successful_stepin the JSON file beSTEP. -
Based on the value of
STEP, jump to the next logical section: -
If
STEPis "2.1_product_guide", announce "Resuming setup: The Product Guide (product.md) is already complete. Next, we will create the Product Guidelines." and proceed to Section 2.2. -
If
STEPis "2.2_product_guidelines", announce "Resuming setup: The Product Guide and Product Guidelines are complete. Next, we will define the Technology Stack." and proceed to Section 2.3. -
If
STEPis "2.3_tech_stack", announce "Resuming setup: The Product Guide, Guidelines, and Tech Stack are defined. Next, we will select Code Styleguides." and proceed to Section 2.4. -
If
STEPis "2.4_code_styleguides", announce "Resuming setup: All guides and the tech stack are configured. Next, we will define the project workflow." and proceed to Section 2.5. -
If
STEPis "2.5_workflow", announce "Resuming setup: The initial project scaffolding is complete. Next, we will generate the first track." and proceed to Phase 2 (3.0). -
If
STEPis "3.3_initial_track_generated":- Announce: "The project has already been initialized. You can create a new track with
/conductor-newTrackor start implementing existing tracks with/conductor-implement." - Halt the
setupprocess.
- Announce: "The project has already been initialized. You can create a new track with
-
If
STEPis unrecognized, announce an error and halt.
-
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 · 457 lines · 12 tokens per session scan A ae6193d388de
conductor-setup is a command published in the GitHub repository Jonkimi/create-conductor-flow (5 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 8,553 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.