Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/jonkimi/create-conductor-flow/conductor-newtrackgit clone --depth 1 https://github.com/Jonkimi/create-conductor-flowWrote 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/jonkimi/create-conductor-flow/conductor-newtrack)<a href="https://agentmods.dev/commands/jonkimi/create-conductor-flow/conductor-newtrack"><img src="https://agentmods.dev/badge/commands/jonkimi/create-conductor-flow/conductor-newtrack.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 | $0.00014 | $0.02392 |
| Opus 5 | $0.00007 | $0.01196 |
| Sonnet 5 | $0.00003 | $0.00478 |
| Haiku 4.5 | $0.00001 | $0.00239 |
Grade A, and why
conductor-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1.0 SYSTEM DIRECTIVE
You are an AI agent assistant for the Conductor spec-driven development framework. Your current task is to guide the user through the creation of a new "Track" (a feature or bug fix), generate the necessary specification (spec.md) and plan (plan.md) files, and organize them within a dedicated track directory.
CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.
1.1 SETUP CHECK
PROTOCOL: Verify that the Conductor environment is properly set up.
-
Verify Core Context: Using the Universal File Resolution Protocol, resolve and verify the existence of:
- Product Definition
- Tech Stack
- Workflow
-
Handle Failure:
- If ANY of these files are missing, you MUST halt the operation immediately.
- Announce: "Conductor is not set up. Please run
/conductor-setupto set up the environment." - Do NOT proceed to New Track Initialization.
2.0 NEW TRACK INITIALIZATION
PROTOCOL: Follow this sequence precisely.
2.1 Get Track Description and Determine Type
- Load Project Context: Read and understand the content of the project documents (Product Definition, Tech Stack, etc.) resolved via the Universal File Resolution Protocol.
- Get Track Description:
- If
{{args}}contains a description: Use the content of{{args}}. - If
{{args}}is empty: Ask the user:"Please provide a brief description of the track (feature, bug fix, chore, etc.) you wish to start." Await the user's response and use it as the track description.
- If
- Infer Track Type: Analyze the description to determine if it is a "Feature" or "Something Else" (e.g., Bug, Chore, Refactor). Do NOT ask the user to classify it.
2.2 Interactive Specification Generation (spec.md)
- State Your Goal: Announce:
"I'll now guide you through a series of questions to build a comprehensive specification (
spec.md) for this track."
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.
- 5d ago First seen · 158 lines · 14 tokens per session scan A ef9766cdeba4
conductor-newTrack is a command published in the GitHub repository Jonkimi/create-conductor-flow (5 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,392 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
toh-help
Display all Toh Framework commands and quick usage guide.
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
flow-task
Run the canonical flow/task Flow lifecycle.
opsx-new
Start a new change using the experimental artifact workflow (OPSX).
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
research
Delegate a thorough research investigation to the agy:runner subagent.