Conductor-Beads: Command for Claude Code

.claude/commands/conductor-setup.md

conductor-setup is a command for Claude Code from NguyenSiTrung/Conductor-Beads. It costs 8 tokens per session (3,434 once invoked), scanned C, original, Apache-2.0.

A command that initializes a project with Conductor's structured development workflow. It creates project guidance, such as product, technology, coding-style, workflow, and task-planning documents.

In plain words
What is it for?
Use it to set up Conductor, answer questions about the product and technology, create project guidelines, and generate the first planned work track.
Why use it?
It gives a new project shared written context and a resumable plan, so development work does not depend only on conversation history.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is NguyenSiTrung/Conductor-Beads's own configuration. It tells Claude Code how to work on Conductor-Beads 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 Conductor-Beads configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is *Link: [./conductor/tracks/<track_id>/](./conductor/tracks/<track_id>/)*.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/NguyenSiTrung/Conductor-Beads/main/.claude/commands/conductor-setup.md
Clone the repo
git clone --depth 1 https://github.com/NguyenSiTrung/Conductor-Beads

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-setup

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

agentmods 80×15 button for conductor-setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/conductor-setup"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,434 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00008 $0.03434
Opus 5 $0.00004 $0.01717
Sonnet 5 $0.00002 $0.00687
Haiku 4.5 $0.00001 $0.00343

Measured 9d ago against content hash b105b97ade1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade C, and why

conductor-setup scanned grade C with 1 finding 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 9d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- SYSTEM DIRECTIVE: You are an AI agent. Follow these instructions precisely. CRITICAL: Validate every tool call. If any fails, halt and announce the failure. CRITICAL: When determining model complexity, ALWAYS select
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • setup — 95% identical, 10 lines differ
.claude/commands/conductor-setup.md · 408 lines

How it starts

The opening of the file, as written. The whole thing — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Conductor Setup

Initialize this project with context-driven development. Follow this workflow precisely and sequentially.


1.0 RESUME CHECK

PROTOCOL: Before starting setup, determine the project's state using the state file.

  1. Read State File: Check for conductor/setup_state.json

    • If it does NOT exist, this is a new project. Proceed to Section 1.1.
    • If it exists, read its content.
  2. Resume Based on State: Let last_successful_step be STEP:

    • If STEP is "2.1_product_guide": Announce "Resuming: Product Guide complete. Next: Product Guidelines." → Proceed to Section 2.2
    • If STEP is "2.2_product_guidelines": Announce "Resuming: Guidelines complete. Next: Tech Stack." → Proceed to Section 2.3
    • If STEP is "2.3_tech_stack": Announce "Resuming: Tech Stack complete. Next: Code Styleguides." → Proceed to Section 2.4
    • If STEP is "2.4_code_styleguides": Announce "Resuming: Styleguides complete. Next: Workflow." → Proceed to Section 2.5
    • If STEP is "2.5_workflow": Announce "Resuming: Scaffolding complete. Next: Initial Track." → Proceed to Phase 2 (Section 3.0)
    • If STEP is "3.3_initial_track_generated" or "complete":
      • Announce: "Project already initialized. Use /conductor-newtrack or /conductor-implement."
      • HALT the setup process.
    • If STEP is unrecognized: Announce error and halt.

1.1 PRE-INITIALIZATION OVERVIEW

Present to user:

"Welcome to Conductor. I will guide you through:

  1. Project Discovery: Analyze if this is new or existing project
  2. Product Definition: Define vision, guidelines, and tech stack
  3. Configuration: Select code style guides and workflow
  4. Track Generation: Create the initial development track

Let's get started!"

Read the full file on GitHub · 408 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. 9d ago First seen · 408 lines · 8 tokens per session scan C b105b97ade1b

Subscribe to this mod's changes

conductor-setup is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 3,434 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.