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 agentmods add skills/gemini-cli-extensions/conductor/conductor-reviewnpx skills add gemini-cli-extensions/conductor --skill conductor-reviewgit 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-review)<a href="https://agentmods.dev/skills/gemini-cli-extensions/conductor/conductor-review"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/conductor/conductor-review.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.00027 | $0.03183 |
| Opus 5 | $0.00014 | $0.01591 |
| Sonnet 5 | $0.00005 | $0.00637 |
| Haiku 4.5 | $0.00003 | $0.00318 |
Grade A, and why
conductor-review 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor Review Skill
You are an AI agent acting as a Principal Software Engineer and Code Review Architect. Your goal is to review the implementation of a specific track or a set of changes against the project's standards, design guidelines, and the original plan.
Persona:
- You think from first principles.
- You are meticulous and detail-oriented.
- You prioritize correctness, maintainability, and security over minor stylistic nits (unless they violate strict style guides).
- You are helpful but firm in your standards.
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.
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 · 223 lines · 27 tokens per session scan A a1c83c807f8f
conductor-review is a skill published in the GitHub repository gemini-cli-extensions/conductor (3,729 stars, last pushed 3d ago), licensed Apache-2.0. It adds 27 tokens to every session and 3,183 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-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.
mantis-reproduce
Generates and runs crash reproducers to verify security flaws. Use when viable findings exist and you need to write and execute a script or payload to verify the crash. Don't use for code auditing or patching.
mantis-plan
Formulates a targeted defensive security reviewing plan based on the active threat model and historical learnings. Use when starting a security review campaign to map the codebase boundaries and generate a roadmap (workspace/plan.json). Don't use for executing code reviews, writing test scripts, or patching code.
mantis-report
Generates a human-readable security review packet compiled from confirmed findings and exploit chains. Use at the end of a review cycle to produce stakeholder-facing documentation. Don't use for auditing code or verifying patches directly.
mantis-dedupe
Consolidates raw security findings to eliminate redundant reports. Use when raw findings have been generated by the researcher and need consolidation before review. Don't use for initial code auditing or patch generation.
mantis-history
Analyzes the repository's version control system (VCS) history to extract past vulnerabilities, security fixes, and vulnerability patterns. Use as an initial pre-processing step to build a historical vulnerabilities database (workspace/historicallearnings.jsonl) that informs subsequent stages about past issues and…