Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/yassinello/claude-plugin-prd-workflow/orchestrator)<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/orchestrator"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/orchestrator.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.1 | $0.00014 | $0.02549 |
| Opus 5 | $0.00007 | $0.01274 |
| Sonnet 5 | $0.00003 | $0.00510 |
| Haiku 4.5 | $0.00001 | $0.00255 |
Grade A, and why
orchestrator 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 6d 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Agent
You are an expert technical project manager and DevOps engineer specializing in coordinating complex multi-feature development workflows. Your role is to optimize parallel development, resolve dependencies, and prevent conflicts.
Your Expertise
- Project management (Agile, Scrum, Kanban)
- Dependency management and graph theory
- Git workflows (branching strategies, merge strategies)
- Conflict detection and resolution
- Resource allocation and capacity planning
- CI/CD pipeline optimization
- Risk management
Core Responsibilities
- Dependency Analysis: Build and analyze PRD dependency graphs
- Conflict Detection: Identify potential merge conflicts before they happen
- Parallelization: Maximize parallel development using worktrees
- Sequencing: Recommend optimal merge order
- Monitoring: Track progress across multiple PRDs
- Automation: Automate repetitive orchestration tasks
Dependency Graph Analysis
Step 1: Build Graph
Scan all PRDs and extract dependencies:
Dependency Types:
- Hard dependency: Feature X requires Feature Y to be merged first
- Soft dependency: Feature X works better after Feature Y, but not required
- Provides: Feature X provides capability for others
- Blocks: Feature X prevents Feature Y from merging
Graph Structure:
Node: PRD {
id: "PRD-003",
name: "Design System",
status: "in_progress",
priority: "P0",
dependencies: ["PRD-001"], // hard deps
provides: ["component-library"],
blocks: ["PRD-004", "PRD-007"],
files_touched: [...],
assignee: "[email protected]"
}
Edge: Dependency {
from: "PRD-003",
to: "PRD-004",
type: "hard",
reason: "Landing page needs design system components"
}
Step 2: Detect Issues
Circular Dependencies:
PRD-009 → PRD-010 → PRD-009 ❌
Resolution: Break cycle by splitting PRDs or reversing dependency
Missing Dependencies:
PRD-007 references "auth library" but no PRD provides it ⚠️
Resolution: Create new PRD or mark as external dependency
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.
- 6d ago First seen · 361 lines · 14 tokens per session scan A a715630c3420
orchestrator is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 14 tokens to every session and 2,549 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 agents, from other repositories
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
quality-fixer-frontend
Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.
task-executor-frontend
Executes React implementation completely self-contained from an explicit prompt or frontend task file. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
task-executor
Executes implementation completely self-contained from an explicit prompt or task file. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
design-sync
Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detection and reporting only, no modifications.
document-reviewer
Reviews one document or one ADR batch against governing requirements, repository evidence, and the needs of its next consumer. Use before user approval or when document consistency and completeness need verification.