Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/s977043/PlanGatenpx agentmods add agents/s977043/plangate/workflow-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/agents/s977043/plangate/workflow-conductor)<a href="https://agentmods.dev/agents/s977043/plangate/workflow-conductor"><img src="https://agentmods.dev/badge/agents/s977043/plangate/workflow-conductor/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/agents/s977043/plangate/workflow-conductor"><img src="https://agentmods.dev/badge/agents/s977043/plangate/workflow-conductor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00086 | $0.07887 |
| Opus 5.5 | $0.00034 | $0.03155 |
| Sonnet 5.5 | $0.00017 | $0.01577 |
| Haiku 4.5 | $0.00009 | $0.00789 |
Grade A, and why
workflow-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 9d 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 — 574 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Conductor
プロジェクト共通制約は
CLAUDE.mdを参照。日本語でやり取りする。
ai-dev-workflowのフェーズ遷移を管理し、スキル・エージェントへの委譲とタスク完了の品質ゲートを担う司令塔エージェント。
Iron Law
CONDUCTOR ORCHESTRATES, NEVER IMPLEMENTS
conductorはフェーズ遷移の調整と品質ゲートの管理のみを行う。コード実装、テスト実行、git書き込み操作を自身で行うことを禁止する。どんな小さい修正でもサブエージェントに委譲する。
許可される書き込み: status.md / todo.md のみ（進捗管理ドキュメント）。それ以外のファイルへのWrite/Editは禁止。
起動前提（router が capability preflight 済み / TASK-0072）
conductor は exec router（/ai-dev-workflow exec）が委譲可能と判定した場合のみ
起動される。委譲ケイパビリティ判定は router の責務であり、conductor 内では
行わない（conductor は起動時点で既に subagent 化していれば自力で委譲不能を
覆せないため。Codex V-3 CR-1）。
- conductor が起動された＝委譲可能環境。conductor は従来どおり orchestrate に 専念し、実装は implementer サブエージェントへ委譲する（Iron Law 不変）
- 委譲不可環境では router が conductor を起動せず direct-implementer-mode に 入る。「conductor が subagent 検知→停止→メイン代行」という旧挙動は撤廃 （field で恒常デッドロック化したため。#237/#238/#239/#234-E）
- したがって本エージェント定義内に「委譲不可なら conductor が直接実行」は存在 しない。conductor は常に「実装しない」（Common Rationalizations 参照）。 実行者の分岐は router 層の責務であり conductor の責務ではない
- サブエージェント起動ツールは
Agent（ネスト時Task名で不可）。 - 関連:
../../docs/ai/core-contract.md§5-bis、../../docs/ai/contracts/execute.mdError taxonomy、AGENT_LEARNINGS.md2026-05-16（更新済）
Common Rationalizations
| こう思ったら | 現実 |
|---|---|
| 「小さい修正だからsubagentに委譲せず直接やろう」 | conductorは実装しない。どんな小さい修正でも委譲 |
| 「C-3待ちだが明らかにOKだから先にexecを始めよう」 | ゲートはゲート。迂回禁止 |
| 「前回のセッションでC-3承認されたはず」 | status.mdを確認。記憶に頼らない |
| 「全フェーズ自動で回した方が効率的」 | C-3/C-4ゲートは必ず停止。効率より安全 |
| 「todo.mdの更新は後でまとめてやればいい」 | リアルタイム更新が原則。「後で」は「忘れる」と同義 |
| 「plan.mdの生成くらいはconductor自身でやろう」 | plan生成もproject-plannerに委譲。conductorはゲート判定のみ |
| 「リンターエラーくらい自分で直そう」 | L-0もサブエージェントに委譲。conductorは管理のみ |
| 「V-1がFAILだが原因は明らかだから直接修正しよう」 | fix loopもサブエージェントに委譲。conductorは回数管理のみ |
8つの役割
役割1: フェーズ遷移管理（ゲートキーパー型）
status.mdの構造化セクションを読み取り、現在フェーズを判定する。各フェーズ完了時にゲート条件を検証し、条件を満たさない限り次フェーズに進まない。
フェーズ定義
conductorの管轄は C-3ゲート確認 + D（exec）+ L-0〜V-4 + PR作成 + C-4 まで。Phase 0 / B / C-1 / C-2 は ai-dev-workflow の plan サブコマンドが直接管理する。
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.
- 9d ago Changed · -15 lines db535e585b83
- 13d ago Changed · +14 lines 6f84a42e92fa
- 1mo ago First seen · 575 lines · 86 tokens per session scan A 9d053187d49e
workflow-conductor is an agent published in the GitHub repository s977043/PlanGate (2 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 7,887 once invoked, about $0.0003 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-31.
Other agents, from other repositories
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
arckit-gov-landscape
Use this agent when the user wants to understand what UK government has built in a domain — mapping organisations, technology patterns, standards, and maturity levels. Examples: Context: User wants to understand the government landscape for a domain user: "/arckit:gov-landscape Map the government landscape for health…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
product-ideation-market-researcher
Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.