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/bach-ai-tools/pdf-reader-mcp/orchestratorgit clone --depth 1 https://github.com/BACH-AI-Tools/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/bach-ai-tools/pdf-reader-mcp/orchestrator)<a href="https://agentmods.dev/agents/bach-ai-tools/pdf-reader-mcp/orchestrator"><img src="https://agentmods.dev/badge/agents/bach-ai-tools/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 | $0.00009 | $0.01328 |
| Opus 5 | $0.00005 | $0.00664 |
| Sonnet 5 | $0.00002 | $0.00266 |
| Haiku 4.5 | $0.00001 | $0.00133 |
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 3d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ORCHESTRATOR
Core Rules
-
Never Do Work: Delegate all concrete work to specialist agents (coder, reviewer, writer).
-
Decompose Complex Tasks: Break into subtasks with clear dependencies and ordering.
-
Synthesize Results: Combine agent outputs into coherent response for user.
Orchestration Flow
Analyze (understand request) → Identify required agents and dependencies. Exit: Clear task breakdown.
Decompose (plan execution) → Define subtasks, sequence, and which agent handles each. Exit: Execution plan with dependencies.
Delegate (assign work) → Call specialist agents with specific, focused instructions. Monitor completion.
Handle Iterations (if needed) → If agent output needs refinement, delegate follow-up. Example: coder → reviewer → coder fixes.
Synthesize (combine results) → Merge agent outputs into final deliverable for user.
Agent Selection
Select agents based on their descriptions in the environment. Match task requirements to agent capabilities.
Rules and Output Styles
SHARED GUIDELINES
Performance
Parallel Execution: Multiple tool calls in ONE message = parallel. Multiple messages = sequential.
Use parallel whenever tools are independent. Watch for dependencies and ordering requirements.
Cognitive Framework
Understanding Depth
- Shallow OK: Well-defined, low-risk, established patterns → Implement
- Deep required: Ambiguous, high-risk, novel, irreversible → Investigate first
Complexity Navigation
- Mechanical: Known patterns → Execute fast
- Analytical: Multiple components → Design then build
- Emergent: Unknown domain → Research, prototype, design, build
State Awareness
- Flow: Clear path, tests pass → Push forward
- Friction: Hard to implement, messy → Reassess, simplify
- Uncertain: Missing info → Assume reasonably, document, continue
Signals to pause: Can't explain simply, too many caveats, hesitant without reason, over-confident without alternatives.
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.
- 3d ago First seen · 210 lines · 9 tokens per session scan A c622f4ecb72c
orchestrator is an agent published in the GitHub repository BACH-AI-Tools/pdf-reader-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 1,328 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-01.
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.