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.
git clone --depth 1 https://github.com/thapaliyabikendra/ai-artifactsWrote 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/thapaliyabikendra/ai-artifacts/orchestration-patterns)<a href="https://agentmods.dev/agents/thapaliyabikendra/ai-artifacts/orchestration-patterns"><img src="https://agentmods.dev/badge/agents/thapaliyabikendra/ai-artifacts/orchestration-patterns/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/thapaliyabikendra/ai-artifacts/orchestration-patterns"><img src="https://agentmods.dev/badge/agents/thapaliyabikendra/ai-artifacts/orchestration-patterns.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.00000 | $0.02462 |
| Opus 5.5 | $0.00000 | $0.00985 |
| Sonnet 5.5 | $0.00000 | $0.00492 |
| Haiku 4.5 | $0.00000 | $0.00246 |
Grade A, and why
orchestration-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Patterns for Multi-Agent Systems
Overview
The orchestrator (master agent) coordinates specialized sub-agents using different patterns based on task requirements. This document covers the two primary orchestration strategies and when to use each.
Pattern 1: Parallel Execution (Fan-Out/Fan-In)
When to Use
- Multiple independent analyses needed
- Time-sensitive tasks that can run concurrently
- Information gathering phase before decision-making
- No dependencies between sub-agent tasks
How It Works
┌────────────────┐
│ Orchestrator │
│ (Main Session) │
└───────┬────────┘
│ spawns all at once
┌──────────────────┼──────────────────┐
│ │ │
▼ ▼ ▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ backend- │ │ security- │ │ qa- │
│ architect │ │ engineer │ │ engineer │
│ │ │ │ │ │
│ Designs TSD │ │ Audits security │ │ Plans tests │
└────────┬────────┘ └────────┬────────┘ └────────┬────────┘
│ │ │
└───────────────────┴───────────────────┘
│ all complete
▼
┌────────────────┐
│ Orchestrator │
│ Consolidates │
│ all outputs │
└────────────────┘
Example Use Cases
1. Requirements Analysis Phase
Orchestrator spawns:
├── product-manager → Analyzes business requirements
├── backend-architect → Explores technical feasibility
└── security-engineer → Identifies security concerns
Consolidation: Combined analysis report with recommendations
2. Pre-Implementation Review
Orchestrator spawns:
├── abp-code-reviewer → Reviews existing backend patterns
├── security-engineer → Checks for vulnerabilities
└── qa-engineer → Analyzes test coverage
Consolidation: Go/no-go decision with action items
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 · 367 lines · 0 tokens per session scan A d02afaa21464
orchestration-patterns is an agent published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,462 tokens. 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.