Conductor is a command-line tool for defining and running workflows in which multiple AI agents perform connected tasks. Developers use YAML files to create repeatable pipelines for activities such as code review, research and synthesis, or planning and implementation, with routing handled by explicit conditions. The catalogue add-ons provide instructions, skills, plugins, and an agent for working with Conductor.
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 microsoft/conductor --skill release-notesgit clone --depth 1 https://github.com/microsoft/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/microsoft/conductor/release-notes)<a href="https://agentmods.dev/skills/microsoft/conductor/release-notes"><img src="https://agentmods.dev/badge/skills/microsoft/conductor/release-notes/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/microsoft/conductor/release-notes"><img src="https://agentmods.dev/badge/skills/microsoft/conductor/release-notes.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.00031 | $0.00234 |
| Opus 5.5 | $0.00012 | $0.00094 |
| Sonnet 5.5 | $0.00006 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
release-notes 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.
What it actually says
Release notes
Write notes for the people who use the software, not the people who wrote it.
Process
- Group changes by what a user would notice: new capabilities, fixed behaviour, and things that now work differently.
- Drop anything with no user-visible effect — refactors, test changes, dependency bumps that changed nothing observable.
- Lead each entry with the effect, not the mechanism. "Workflows resume after a dashboard stop" beats "added handle_dashboard_stop".
Delegating
When the notes need a second opinion on tone or padding, hand the draft to
the demo:editor subagent rather than revising in place. It is tuned to cut
filler, and asking it is the point of enabling this plugin — the skill and
the subagent ship together.
Output
A short intro line, then grouped bullets. No version numbers unless you were given one.
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 · 31 lines · 31 tokens per session scan A 7eb854a54bae
release-notes is a skill published in the GitHub repository microsoft/conductor (476 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 234 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.