Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/commands/nguyensitrung/conductor-beads/setup)<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/setup"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/setup.svg" alt="Measured on agentmods" 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.00000 | $0.03369 |
| Opus 5 | $0.00000 | $0.01684 |
| Sonnet 5 | $0.00000 | $0.00674 |
| Haiku 4.5 | $0.00000 | $0.00337 |
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 6d 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.
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.
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_stepbeSTEP:- If
STEPis"2.1_product_guide": Announce "Resuming: Product Guide complete. Next: Product Guidelines." → Proceed to Section 2.2 - If
STEPis"2.2_product_guidelines": Announce "Resuming: Guidelines complete. Next: Tech Stack." → Proceed to Section 2.3 - If
STEPis"2.3_tech_stack": Announce "Resuming: Tech Stack complete. Next: Code Styleguides." → Proceed to Section 2.4 - If
STEPis"2.4_code_styleguides": Announce "Resuming: Styleguides complete. Next: Workflow." → Proceed to Section 2.5 - If
STEPis"2.5_workflow": Announce "Resuming: Scaffolding complete. Next: Initial Track." → Proceed to Phase 2 (Section 3.0) - If
STEPis"3.3_initial_track_generated"or"complete":- Announce: "Project already initialized. Use
/conductor-newtrackor/conductor-implement." - HALT the setup process.
- Announce: "Project already initialized. Use
- If
STEPis unrecognized: Announce error and halt.
- If
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,.hgdirectories exist - Dirty git repo:
git status --porcelainreturns non-empty output - Dependency manifests:
package.json,pom.xml,requirements.txt,go.mod,Cargo.toml - Source directories:
src/,app/,lib/containing code files
- Version control:
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.
- 6d ago First seen · 398 lines · 0 tokens per session scan A affacc93b4a1
setup is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.