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-implementgit 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-implement)<a href="https://agentmods.dev/skills/gemini-cli-extensions/conductor/conductor-implement"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/conductor/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.
<a href="https://agentmods.dev/skills/gemini-cli-extensions/conductor/conductor-implement"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/conductor/conductor-implement.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.00034 | $0.02196 |
| Opus 5.5 | $0.00014 | $0.00878 |
| Sonnet 5.5 | $0.00007 | $0.00439 |
| Haiku 4.5 | $0.00003 | $0.00220 |
Grade A, and why
conductor-implement 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 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.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor Implement Skill
You are the Conductor Implementer. Your goal is to execute the tasks defined in the specified track's plan following the Spec-Driven Development (SDD) framework. This document is your operational protocol: adhere to it precisely and sequentially.
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). - 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 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.
- 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.
1. Handshake & Context Initialization
Before starting the implementation process, you MUST locate and read the project's foundational context.
- Locate Index: Check for the existence of
conductor/index.mdin the project root.- If Missing:
- Announce: "Conductor is not initialized properly. I cannot find the
conductor/index.mdfile." - Ask the user using a Yes/No question if they would like to run the setup process now to initialize Conductor.
- If Approved: Internally invoke the
conductor-setupskill. - If Denied: HALT and await further instructions.
- Announce: "Conductor is not initialized properly. I cannot find the
- If Missing:
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 · 140 lines · 34 tokens per session scan A fbb99802ab9e
conductor-implement is a skill published in the GitHub repository gemini-cli-extensions/conductor (3,770 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,196 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
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.
biblemate
Orchestrate the entire BibleMate AI study workflow dynamically using available skills.
biblemate-super
Run a dynamically planned, multi-phase BibleMate-Super study, orchestrating specialized skills and personas with dynamic audit checkpoints.
dictionaries
Retrieve dictionary data for specific words or phrases from local databases.
encyclopedias
Retrieve encyclopedia data for specific words or phrases from local databases.
parallels
Retrieve and analyze parallel Bible passages, comparing their similarities, differences, theological significance, and life applications.