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 commands/yassinello/claude-plugin-prd-workflow/orchestrategit clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWrote 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/commands/yassinello/claude-plugin-prd-workflow/orchestrate)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/orchestrate"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/orchestrate.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.00015 | $0.03082 |
| Opus 5 | $0.00008 | $0.01541 |
| Sonnet 5 | $0.00003 | $0.00616 |
| Haiku 4.5 | $0.00002 | $0.00308 |
Grade A, and why
orchestrate 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate Command
Coordinate parallel development of multiple PRDs with automatic dependency resolution and conflict prevention.
Purpose
Enable efficient multi-feature development:
- Visualize PRD dependencies
- Suggest optimal development order
- Coordinate parallel work (using worktrees)
- Prevent merge conflicts
- Track cross-PRD blockers
- Automate sequential merges
Workflow
Step 1: Analyze PRD Landscape (Parallel Execution)
NEW: Parallel Analysis for Speed
Instead of analyzing PRDs sequentially (slow), analyze all in parallel:
// OLD (Sequential - SLOW):
for (const prd of allPRDs) {
await analyzePRD(prd); // 10s per PRD × 10 PRDs = 100s total
}
// NEW (Parallel - FAST):
await Promise.all(
allPRDs.map(prd => analyzePRD(prd)) // All at once = 10s total
);
Performance Impact:
- 10 PRDs: 100s → 10s (-90%)
- 20 PRDs: 200s → 10s (-95%)
Scan all PRDs across statuses and extract (in parallel):
- PRD dependencies (declared in PRDs)
- File overlap (potential conflicts)
- Priority levels
- Current status (draft/review/ready/in-progress)
- Developer assignments (if tracked)
🔍 Analyzing PRDs...
⚡ Parallel analysis of 10 PRDs:
[████████████████████] PRD-001 ✓
[████████████████████] PRD-002 ✓
[████████████████████] PRD-003 ✓
[████████████████████] PRD-004 ✓
[████████████████████] PRD-005 ✓
[████████████████████] PRD-006 ✓
[████████████████████] PRD-007 ✓
[████████████████████] PRD-008 ✓
[████████████████████] PRD-009 ✓
[████████████████████] PRD-010 ✓
✅ Analysis complete in 12s (vs 120s sequential)
Step 2: Build Dependency Graph
Create directed graph:
- Nodes = PRDs
- Edges = dependencies
- Edge labels = dependency type (hard/soft)
Detect:
- ✅ Valid linear chains (A → B → C)
- ✅ Parallel branches (A → C, B → C)
- ⚠️ Circular dependencies (A → B → A)
- ⚠️ Missing dependencies
Step 3: Identify Conflicts (Parallel Execution)
NEW: Parallel Conflict Detection
Analyze all PRD pairs in parallel instead of sequentially:
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 · 400 lines · 15 tokens per session scan A bbd0cd906df2
orchestrate is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 3,082 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 commands, from other repositories
brooks-debt
Run a Brooks-Lint tech debt assessment.
brooks-health
Run a Brooks-Lint codebase health dashboard across all four dimensions.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.