conductor-setup

A project setup command for the Conductor methodology, a way of organizing software work with project guidance and saved setup progress.

In plain words
What is it for?
Use it to initialize a project for Conductor-based work and create its product guide and related setup files.
Why use it?
It provides a defined setup process and can resume from the last completed step if setup was interrupted.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/jonkimi/create-conductor-flow/conductor-setup
Clone the repo
git clone --depth 1 https://github.com/Jonkimi/create-conductor-flow

Made for: Claude Code.

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 8,553 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.08553
Opus 5 $0.00006 $0.04276
Sonnet 5 $0.00002 $0.01711
Haiku 4.5 $0.00001 $0.00855

Measured yesterday against content hash ae6193d388de, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.claude/commands/conductor-setup.md · 457 lines

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.

  1. 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.
  2. Resume Based on State:

    • Let the value of last_successful_step in the JSON file be STEP.

    • Based on the value of STEP, jump to the next logical section:

    • If STEP is "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 STEP is "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 STEP is "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 STEP is "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 STEP is "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 STEP is "3.3_initial_track_generated":

      • Announce: "The project has already been initialized. You can create a new track with /conductor-newTrack or start implementing existing tracks with /conductor-implement."
      • Halt the setup process.
    • If STEP is unrecognized, announce an error and halt.

Read the full file on GitHub · 457 lines

Changes

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.

  1. yesterday First seen · 457 lines · 12 tokens per session scan A ae6193d388de

Subscribe to this mod's changes

conductor-setup is a command published in the GitHub repository Jonkimi/create-conductor-flow (5 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 8,553 once invoked, about $0.0001 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-31.