conductor

A workflow tool for coordinating multiple coding agents through YAML files, a text format for structured configuration. It can validate, run, and execute these multi-agent workflows.

In plain words
What is it for?
Use it to build and run automated workflows where several agents have different tasks. It helps manage agent steps, configuration, and execution from YAML.
Why use it?
It provides a defined way to describe which agents should work together and how the workflow should run. Validation can catch workflow-configuration problems before execution.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add microsoft/conductor
agentmods
npx agentmods add plugins/microsoft/conductor/marketplace
Clone the repo
git clone --depth 1 https://github.com/microsoft/conductor

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

conductor 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 yesterday.

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.

.claude-plugin/marketplace.json · 36 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
  "name": "conductor",
  "version": "0.1.15",
  "description": "Conductor — multi-agent workflow orchestration via YAML",
  "owner": {
    "name": "Microsoft",
    "email": "[email protected]"
  },
  "metadata": {
    "pluginRoot": "./plugins"
  },
  "plugins": [
    {
      "name": "conductor",
      "source": "./conductor",
      "description": "Validate, run, and execute Conductor multi-agent YAML workflows. Adds the conductor skill that knows the workflow schema, CLI commands, and execution model.",
      "author": { "name": "Microsoft" },
      "homepage": "https://github.com/microsoft/conductor",
      "repository": "https://github.com/microsoft/conductor",
      "license": "MIT",
      "category": "workflow",
      "keywords": [
        "workflow",
        "orchestration",
        "multi-agent",
        "yaml",
        "copilot",
        "claude",
        "agents"
      ],
      "tags": ["agents", "automation", "workflow"]
    }
  ]
}
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. yesterday First seen · 36 lines scan A 52f9afda2a34

Subscribe to this mod's changes

conductor is a plugin published in the GitHub repository microsoft/conductor (408 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.