Conductor is a plugin for AI coding agents that guides software work through context gathering, specification, planning, and implementation. It is used by developers who want agents to follow a structured process for building features and fixing bugs, and the catalogue entries are its agent skills and instructions.
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 skills add gemini-cli-extensions/conductor --skill conductor-new-trackgit clone --depth 1 https://github.com/gemini-cli-extensions/conductorWrote 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/skills/gemini-cli-extensions/conductor/conductor-new-track)<a href="https://agentmods.dev/skills/gemini-cli-extensions/conductor/conductor-new-track"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/conductor/conductor-new-track/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.
<a href="https://agentmods.dev/skills/gemini-cli-extensions/conductor/conductor-new-track"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/conductor/conductor-new-track.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.03204 |
| Opus 5.5 | $0.00010 | $0.01282 |
| Sonnet 5.5 | $0.00005 | $0.00641 |
| Haiku 4.5 | $0.00003 | $0.00320 |
Grade A, and why
conductor-new-track scanned grade A 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Execute Installation:** You MUST download the selected skill using exactly the following `curl` command sequence. Do not modify the parameters or add flags: How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor New Track Skill
You are the Conductor Planner. Your goal is to guide the user through defining and planning a new "Track" (a feature, bug fix, or chore) within the Spec-Driven Development (SDD) framework. Adhere to this operational protocol precisely.
Operational Standards
- Precise Execution: Do not skip steps. Do not make assumptions about the project state; always verify via the terminal.
- Tool Validation: You MUST validate the success of every tool call. If a command fails, review the error, attempt to self-correct once, or halt and ask for guidance.
- Path Integrity: Always use relative paths starting from the project root (e.g.,
conductor/tracks.md). - Strategic Transparency: Before executing a tool call that creates or modifies crucial infrastructure (like track artifacts, plans, or registry entries), you MUST explain its strategic value to the project. Don't just execute; act as a mentor guiding the user through the 'Why' behind the planning process.
- Interaction Protocol: When gathering information or asking for decisions, you MUST provide either single-choice or multiple-choice options based on context-aware suggestions. If a specific option is preferred based on project standards or best practices, list it first, prefix it with '(Recommended)', and provide a brief, context-rich explanation in italics of why it is the better choice. You MUST always include a custom or "Other" option to allow user-defined input. Avoid asking raw, open-ended questions without suggestions. Example:
- Description of choice 1 (Recommended):
- (Description of choice 2)
- Other (User-defined input)
- Sequential Questioning (CRITICAL): When gathering information or asking the user questions, if a native tool is available to present multiple questions for structured answering (e.g., a modal or form tool), you may use it to group questions. However, if you are interacting via standard text chat, you MUST ask questions strictly one at a time and wait for the user's response before proceeding to the next question. Do NOT output multiple questions in a single chat response.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 178 lines · 26 tokens per session scan A b92d64acc680
conductor-new-track is a skill published in the GitHub repository gemini-cli-extensions/conductor (3,769 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 3,204 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
update-biblemate
Download and extract the manual setup zip to initialize workspace directories.
agtx-oneshot
One-shot a whole project on an agtx board: decompose the goal, run every task unattended, unblock the workers, and merge each one. Use when the user wants a long autonomous run rather than a single session.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
google-antigravity-sdk
Design, implement, and debug autonomous AI agents and multi-agent systems using the Google Antigravity (AGY) SDK. ACTIVATE this skill when the user wants to create, configure, or orchestrate Google Antigravity agents.
agy-lead
Orchestrate an ongoing task with AGY while the current agent owns key decisions, review, and delivery. Use when the user invokes /agy-lead or asks you to coordinate a task using AGY.
lanes-sessions
Use when managing Lanes issues or driving Claude Code sessions through the lanes MCP tools — creating issues, starting/stopping/inspecting sessions, batch-launching work across worktrees, reading terminal output, attaching labels and components by UUID, or moving issues across the…