Conductor-Beads: Command for Claude Code

.claude/skills/conductor/references/commands/newtrack.md

newtrack is a command for Claude Code from NguyenSiTrung/Conductor-Beads. It costs 0 tokens per session (3,650 once invoked), scanned A, a copy of conductor-newtrack, Apache-2.0.

A command for starting a new Conductor track, which is a planned piece of project work such as a feature, bug fix, or chore. It checks the required project setup and interactively creates a specification file.

In plain words
What is it for?
Use it to initialize a track, classify its type, load project guidance, and create a detailed spec.md through a short question-and-answer process.
Why use it?
It ensures work starts with the needed project context and a documented plan. If Conductor is not set up, it stops and tells you what to do first.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/newtrack"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/newtrack.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,650 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 97% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.03650
Opus 5 $0.00000 $0.01825
Sonnet 5 $0.00000 $0.00730
Haiku 4.5 $0.00000 $0.00365

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

Security

Grade A, and why

newtrack 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 10d 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

97% identical to conductor-newtrack — 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/newtrack.md · 391 lines

How it starts

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

Conductor New Track

Create a new track for: $ARGUMENTS


1.0 SETUP CHECK

PROTOCOL: Verify Conductor environment is properly set up.

  1. Check Required Files: Verify existence of:

    • conductor/product.md
    • conductor/tech-stack.md
    • conductor/workflow.md
  2. Handle Missing Files:

    • If ANY missing: HALT immediately
    • Announce: "Conductor is not set up. Please run /conductor-setup first."
    • Do NOT proceed.

2.0 NEW TRACK INITIALIZATION

2.1 Get Track Description and Determine Type

  1. Load Project Context: Read conductor/ directory files.

  2. Get Track Description:

    • If $ARGUMENTS provided: Use it as track description
    • If empty: Ask:

      "Please provide a brief description of the track (feature, bug fix, chore, etc.) you wish to start." Wait for response.

  3. Infer Track Type: Analyze description to classify as "Feature" or "Something Else" (Bug, Chore, Refactor). Do NOT ask user to classify.


2.2 Interactive Specification Generation (spec.md)

  1. Announce:

    "I'll now guide you through questions to build a comprehensive spec.md for this track."

  2. Questioning Phase (3-5 questions):

    Question Classification - CRITICAL:

    • 1. Classify Question Type: Before EACH question, classify as:

      • Additive: For brainstorming/scope (users, goals, features) - allows multiple answers
      • Exclusive Choice: For singular commitments (specific technology, workflow rule) - single answer
    • 2. Formulate Based on Classification:

      • If Additive: Open-ended question + options + "(Select all that apply)"
      • If Exclusive Choice: Direct question, do NOT add multi-select
    • 3. Interaction Flow:

      • CRITICAL: Ask ONE question at a time. Wait for response before next question.
      • Last option for every question MUST be "Type your own answer"
      • Confirm understanding by summarizing before moving on

    If FEATURE (3-5 questions):

    • Clarifying questions about the feature
    • Implementation approach, interactions, inputs/outputs
    • UI/UX considerations, data involved

Read the full file on GitHub · 391 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. 10d ago First seen · 391 lines · 0 tokens per session scan A fdb36bed5fff

Subscribe to this mod's changes

newtrack 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,650 tokens. A static security scan graded it A with 0 findings. It is 97% identical to conductor-newtrack, differing in 10 lines, and is treated as a copy.