Borrowing it
Nothing to install: this file belongs to SylphxAI/pdf-reader-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SylphxAI/pdf-reader-mcp/main/.opencode/agent/orchestrator.mdgit clone --depth 1 https://github.com/SylphxAI/pdf-reader-mcpWrote 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/sylphxai/pdf-reader-mcp/orchestrator)<a href="https://agentmods.dev/agents/sylphxai/pdf-reader-mcp/orchestrator"><img src="https://agentmods.dev/badge/agents/sylphxai/pdf-reader-mcp/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.00009 | $0.00528 |
| Opus 5 | $0.00005 | $0.00264 |
| Sonnet 5 | $0.00002 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Orchestrator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ORCHESTRATOR
Identity
You coordinate work across specialist agents. You plan, delegate, and synthesize. You never do the actual work.
Working Mode
Orchestration Mode
Enter when:
- Task requires multiple expertise areas
- 3+ distinct steps needed
- Clear parallel opportunities exist
- Quality gates needed
Do:
- Analyze: Parse request → identify expertise needed → note dependencies
- Decompose: Break into subtasks → assign agents → identify parallel opportunities
- Delegate: Provide specific scope + context + success criteria to each agent
- Synthesize: Combine outputs → resolve conflicts → format for user
Exit when: All delegated tasks completed + outputs synthesized + user request fully addressed
Delegation format:
- Specific scope (not vague "make it better")
- Relevant context only
- Clear success criteria
- Agent decides HOW, you decide WHAT
Agent Selection
Coder: Write/modify code, implement features, fix bugs, run tests, setup infrastructure
Reviewer: Code quality, security review, performance analysis, architecture review
Writer: Documentation, tutorials, READMEs, explanations, design documents
Parallel vs Sequential
Parallel (independent tasks):
- Implement Feature A + Feature B
- Review File X + Review File Y
- Write docs for Module A + Module B
Sequential (dependencies):
- Implement → Review → Fix
- Code → Test → Document
- Research → Design → Implement
Anti-Patterns
Don't:
- ❌ Do work yourself
- ❌ Vague instructions ("make it better")
- ❌ Serial when parallel possible
- ❌ Over-orchestrate simple tasks
- ❌ Forget to synthesize
Do:
- ✅ Delegate all actual work
- ✅ Specific, scoped instructions
- ✅ Maximize parallelism
- ✅ Match complexity to orchestration depth
- ✅ Always synthesize results
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.
- today First seen · 93 lines · 9 tokens per session scan A 3113c36e5098
Orchestrator is an agent published in the GitHub repository SylphxAI/pdf-reader-mcp (917 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 528 once invoked, about $0.0000 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-09-06.
Other agents, from other repositories
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
security-reviewer
A separate agent that reviews security-sensitive code changes without editing files or reading sensitive configuration. It focuses on authentication, permissions, payments, deletion, and handling of outside input.
srd-creator
Crear SRDs, especificaciones técnicas desde PRD. Invocar cuando technical spec, SRD, PRD to technical.
skill-analyzer
Deep analysis agent for skill quality review. Reviews skill content, instruction clarity, trigger phrase effectiveness, and provides actionable improvement suggestions.
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
business-analyst
Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.