create-conductor-flow: Command for Claude Code

.claude/commands/conductor-implement.md

conductor-implement is a command for Claude Code from Jonkimi/create-conductor-flow. It costs 11 tokens per session (2,998 once invoked), scanned A, original, Apache-2.0.

A command for implementing a selected track in the Conductor spec-driven development framework, using the project’s defined plans and setup files.

In plain words
What is it for?
Use it to select and execute a planned development track in a Conductor-managed project.
Why use it?
It checks that the required Conductor project context exists before carrying out implementation work.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is Jonkimi/create-conductor-flow's own configuration. It tells Claude Code how to work on create-conductor-flow itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything create-conductor-flow configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Jonkimi/create-conductor-flow/main/.claude/commands/conductor-implement.md
Clone the repo
git clone --depth 1 https://github.com/Jonkimi/create-conductor-flow

Made for: Claude Code.

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

agentmods badge for conductor-implement

README.md
[![agentmods](https://agentmods.dev/badge/commands/jonkimi/create-conductor-flow/conductor-implement/github.svg)](https://agentmods.dev/commands/jonkimi/create-conductor-flow/conductor-implement)
Your own site
<a href="https://agentmods.dev/commands/jonkimi/create-conductor-flow/conductor-implement"><img src="https://agentmods.dev/badge/commands/jonkimi/create-conductor-flow/conductor-implement/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.

agentmods 80×15 button for conductor-implement

Your own site · 80×15
<a href="https://agentmods.dev/commands/jonkimi/create-conductor-flow/conductor-implement"><img src="https://agentmods.dev/badge/commands/jonkimi/create-conductor-flow/conductor-implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,998 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00011 $0.02998
Opus 5.5 $0.00004 $0.01199
Sonnet 5.5 $0.00002 $0.00600
Haiku 4.5 $0.00001 $0.00300

Measured 1mo ago against content hash bf3fbd284e9e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

conductor-implement 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.

.claude/commands/conductor-implement.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 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 assistant for the Conductor spec-driven development framework. Your current task is to implement a track. You MUST follow this protocol precisely.

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.

  1. Verify Core Context: Using the Universal File Resolution Protocol, resolve and verify the existence of:

    • Product Definition
    • Tech Stack
    • Workflow
  2. Handle Failure: If ANY of these are missing (or their resolved paths do not exist), Announce: "Conductor is not set up. Please run /conductor-setup." and HALT.


2.0 TRACK SELECTION

PROTOCOL: Identify and select the track to be implemented.

  1. Check for User Input: First, check if the user provided a track name as an argument (e.g., /conductor-implement <track_description>).

  2. Locate and Parse Tracks Registry:

    • Resolve the Tracks Registry.
    • Read and parse this file. You must parse the file by splitting its content by the --- separator to identify each track section. For each section, extract the status ([ ], [~], [x]), the track description (from the ## heading), and the link to the track folder.
    • CRITICAL: If no track sections are found after parsing, announce: "The tracks file is empty or malformed. No tracks to implement." and halt.
  3. Continue: Immediately proceed to the next step to select a track.

  4. Select Track:

    • If a track name was provided:
      1. Perform an exact, case-insensitive match for the provided name against the track descriptions you parsed.
      2. If a unique match is found, confirm the selection with the user: "I found track '<track_description>'. Is this correct?"
      3. If no match is found, or if the match is ambiguous, inform the user and ask for clarification. Suggest the next available track as below.
    • If no track name was provided (or if the previous step failed):
      1. Identify Next Track: Find the first track in the parsed tracks file that is NOT marked as [x] Completed.
      2. If a next track is found:
        • Announce: "No track name provided. Automatically selecting the next incomplete track: '<track_description>'."
        • Proceed with this track.
      3. If no incomplete tracks are found:
        • Announce: "No incomplete tracks found in the tracks file. All tasks are completed!"
        • Halt the process and await further user instructions.

Read the full file on GitHub · 180 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. 1mo ago First seen · 180 lines · 11 tokens per session scan A bf3fbd284e9e

Subscribe to this mod's changes

conductor-implement is a command published in the GitHub repository Jonkimi/create-conductor-flow (5 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 2,998 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.