A command that initializes a project with context-driven development, a workflow that keeps project decisions, requirements, and progress documented as work proceeds.

It helps create the initial product and technical guidance, choose a technology stack, define code style and workflow rules, scaffold the project, and start its first planned track.

It provides a repeatable setup process and can resume from the last completed step instead of losing project context between sessions.

How NguyenSiTrung/Conductor-Beads configures Claude Code

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/skills/conductor/references/commands/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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/setup/github.svg)](https://agentmods.dev/commands/nguyensitrung/conductor-beads/setup)

Your own site

<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/setup"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/setup"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 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,369 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 95% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.03369
Opus 5.5	$0.00000	$0.01348
Sonnet 5.5	$0.00000	$0.00674
Haiku 4.5	$0.00000	$0.00337

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

Security

Grade A, and why

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 2mo 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.

Origin

This is a copy

95% identical to conductor-setup — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/conductor/references/commands/setup.md · 398 lines

How it starts

The opening of the file, as written. The whole thing — 398 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.

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

Project Discovery: Analyze if this is new or existing project

Product Definition: Define vision, guidelines, and tech stack

Configuration: Select code style guides and workflow

Track Generation: Create the initial development track

Let's get started!"

2.0 PHASE 1: PROJECT SETUP

2.0 Project Inception - Brownfield/Greenfield Detection

Classify Project Maturity:

Brownfield Indicators (ANY match = Brownfield):
- Version control: .git, .svn, .hg directories exist
- Dirty git repo: git status --porcelain returns non-empty output
- Dependency manifests: package.json, pom.xml, requirements.txt, go.mod, Cargo.toml
- Source directories: src/, app/, lib/ containing code files

Read the full file on GitHub · 398 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.

2mo ago First seen · 398 lines · 0 tokens per session scan A affacc93b4a1

Subscribe to this mod's changes

setup is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (23 stars, last pushed 8mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,369 tokens. A static security scan graded it A with 0 findings. It is 95% identical to conductor-setup, differing in 10 lines, and is treated as a copy.

setup next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
setupNguyenSiTrung/Conductor-Beads	Command	23	8mo ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

Conductor-Beads: Command for Claude Code