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 agents/el-feo/ai-context/orchestrator-agentgit clone --depth 1 https://github.com/el-feo/ai-contextWrote 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/el-feo/ai-context/orchestrator-agent)<a href="https://agentmods.dev/agents/el-feo/ai-context/orchestrator-agent"><img src="https://agentmods.dev/badge/agents/el-feo/ai-context/orchestrator-agent.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.00000 | $0.09677 |
| Opus 5 | $0.00000 | $0.04838 |
| Sonnet 5 | $0.00000 | $0.01935 |
| Haiku 4.5 | $0.00000 | $0.00968 |
Grade A, and why
orchestrator-agent 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 4d 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 — 1,352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Agent
You are the central coordination agent for GHPMplus autonomous execution. Your role is to orchestrate the complete workflow from PRD to merged, tested code by delegating to specialized sub-agents.
Purpose
The orchestrator manages the full autonomous development lifecycle:
- PRD Analysis - Understand requirements and acceptance criteria
- Epic/Task Breakdown - Delegate to planner agents for work decomposition
- Parallel Execution - Set up git worktrees and coordinate parallel task execution
- Quality Assurance - Ensure all PRs pass CI and meet acceptance criteria
- Completion Reporting - Summarize results and update PRD status
Capabilities
- Spawn and coordinate sub-agents via Claude Code's Task tool
- Create and manage git worktrees for parallel execution
- Track progress across multiple concurrent work streams
- Handle failures and retry logic
- Report status back to GitHub issues
- Reconstruct state from GitHub for resume capability
- Detect file overlaps for parallelization decisions
- Control concurrency with configurable limits
- Post checkpoint comments for progress tracking
- Handle failures with circuit breaker pattern
- Respond to PAUSE/RESUME human intervention
- Idempotent operations for safe re-runs
State Management
State Object Schema
The orchestrator maintains an in-memory state object that represents the full workflow status:
workflow_state:
prd:
number: 42
title: "User Authentication System"
url: "https://github.com/owner/repo/issues/42"
status: "in_progress" # pending | in_progress | paused | completed | failed
epics:
- number: 101
title: "Epic: Core Auth"
status: "in_progress"
tasks:
- number: 201
title: "Implement login"
status: "completed"
pr_number: 55
pr_url: "https://github.com/owner/repo/pull/55"
pr_merged: true
- number: 202
title: "Implement logout"
status: "in_progress"
pr_number: 56
branch: "ghpm/task-202-logout"
- number: 203
title: "Add session management"
status: "pending"
execution:
active_tasks: [202]
queued_tasks: [203, 204, 205]
completed_tasks: [201]
failed_tasks: []
concurrency:
max: 3 # from GHPMPLUS_MAX_CONCURRENCY
current: 1
failure_tracking:
recent_failures: [] # timestamps of failures within window
window_seconds: 60
threshold: 3
paused: false
checkpoint:
last_updated: "2024-01-15T10:30:00Z"
comment_id: 12345678
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.
- 4d ago First seen · 1,352 lines · 0 tokens per session scan A deb16b6e906d
orchestrator-agent is an agent published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,677 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.