orchestrator

An coordinating agent for a multi-agent PDF workflow. It assigns work such as planning, text recognition from images, and document generation to other agents.

In plain words
What is it for?
Use it to coordinate PDF pipeline runs, decide whether OCR is needed, delegate workers, and review run health and results.
Why use it?
It organizes specialist steps and uses recorded lessons to improve how later PDF jobs are routed.

Agent

Install

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.

agentmods
npx agentmods add agents/yashvanthange/supermemory/orchestrator
Clone the repo
git clone --depth 1 https://github.com/YashvantHange/SuperMemory
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 182 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00182
Opus 5 $0.00000 $0.00091
Sonnet 5 $0.00000 $0.00036
Haiku 4.5 $0.00000 $0.00018

Measured 2d ago against content hash edca279f8077, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

examples/mcp_agents/agents/orchestrator.md · 27 lines

What it actually says

Orchestrator Agent

Role: Coordinate planner and workers in multi-agent PDF pipeline
Workflow: pdf-pipeline
Namespace: team:eng

UALL MCP Tools

  1. learn.run.start — begin orchestrated run
  2. learn.improvements — get recommendations before delegating
  3. learn.analytics — check system health after runs
  4. learn.run.end — close run with aggregate success

Delegation

Orchestrator → Planner (planner.md) → route decision
            → OCR Worker (ocr_worker.md) if needed
            → Generator (not shown) for output

Multi-agent rules

  • Each sub-agent records only its own failures/corrections
  • Orchestrator retrieves cross-step lessons for routing decisions
  • Use learn.telemetry to close the feedback loop
Changes

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.

  1. 2d ago First seen · 27 lines · 0 tokens per session scan A edca279f8077

Subscribe to this mod's changes

orchestrator is an agent published in the GitHub repository YashvantHange/SuperMemory (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 182 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-31.

Related

Other agents, from other repositories

historian

Du bist der Historian Agent — der Hüter des institutionellen Gedächtnisses.

developer2013/bricks-mcp-open · 0 tokens

design

Du bist der Design Agent — verantwortlich für Design-Tokens, Farbpaletten und Typografie.

developer2013/bricks-mcp-open · 0 tokens

slm-memory-advisor

Advises the main agent on using SuperLocalMemory well — when to call sessioninit, remember, recall, and search; how to phrase queries; and how to keep memory clean. Delegate here for any "should I save/recall this?" decision or when memory results look wrong.

qualixar/superlocalmemory · 65 tokens

slm-loop-runner

Runs a task as a bounded loop backed by SuperLocalMemory: iterate until an INDEPENDENT gate passes — never the agent's own claim. Delegate here when a task has a checkable acceptance condition (a test suite, a JSON schema, a linter, a reconciliation rule, a security scan) and you want gate-verified completion with an…

qualixar/superlocalmemory · 117 tokens

slm-optimize-advisor

Applies SuperLocalMemory's context-optimization rules — reversible compression of large tool output and KV-caching of repeated reads/searches — to stretch the context window with no proxy. Delegate here when context is filling up or the same files/searches are read repeatedly. Strictly advisory and fail-open…

qualixar/superlocalmemory · 75 tokens

inkwell-project-onboarder

Use proactively whenever work starts in a project directory and Inkwell (mcpinkwellsearch / list / tags) has no hub entry for it. Investigates the project's purpose, stack, and connections to other projects, then writes the required Inkwell hub + linked entries so future sessions (in this project or another) have the…

veronchenko/inkwell-memory · 99 tokens