Conductor-Beads: Command for Claude Code

.claude/commands/conductor-implement.md

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

A command for carrying out a selected task from a Conductor track, where a track is an implementation plan stored in project files. It first checks that the required Conductor setup and track list exist.

In plain words
What is it for?
Use it to select and implement the next unfinished track, or a named track, from `conductor/tracks.md` after the project setup has been prepared.
Why use it?
It helps follow the project's planned work in order and stops when the planning files are missing, empty, or the requested track cannot be identified.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; mentions AGENTS.md.

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 →

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-implement/github.svg)](https://agentmods.dev/commands/nguyensitrung/conductor-beads/conductor-implement)
Your own site
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/conductor-implement"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/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/nguyensitrung/conductor-beads/conductor-implement"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/conductor-implement.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 6,002 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.06002
Opus 5 $0.00004 $0.03001
Sonnet 5 $0.00002 $0.01200
Haiku 4.5 $0.00001 $0.00600

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

Security

Grade C, and why

conductor-implement 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 for the Conductor framework. CRITICAL: Validate every tool call. If any fails, halt and announce the failure. -->
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

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

How it starts

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

Conductor Implement

Implement track: $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 TRACK SELECTION

PROTOCOL: Identify and select the track to be implemented.

  1. Check for User Input: Check if track name provided as argument.

  2. Parse Tracks File: Read conductor/tracks.md

    • Split by --- separator to identify track sections
    • Extract: status ([ ], [~], [x]), description, folder link
    • CRITICAL: If no track sections found: "The tracks file is empty or malformed." → HALT
  3. Select Track:

    If track name provided:

    • Exact, case-insensitive match against descriptions
    • If unique match: Confirm "I found track ''. Is this correct?"
    • If no match or ambiguous: Inform user, suggest next available track

    If no track name provided:

    • Find first track NOT marked [x]
    • Announce: "No track name provided. Selecting next incomplete track: ''"
    • If all complete: "No incomplete tracks found. All tasks completed!" → HALT
  4. Check Dependencies:

    • Read conductor/tracks/<track_id>/metadata.json
    • If depends_on array is not empty:
      • For each dependency, check status in conductor/tracks.md
      • If ANY not [x] (completed):

        "⚠️ This track has incomplete dependencies:" [List blocking tracks] "Do you want to proceed anyway?" A) Yes - Proceed despite incomplete dependencies B) No - Implement dependencies first

      • If B: Suggest /conductor-implement <first_dependency>

Read the full file on GitHub · 577 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 · 577 lines · 8 tokens per session scan C 114f92c238d3

Subscribe to this mod's changes

conductor-implement 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 6,002 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.