orchestrator

A coordinating agent for an optimization process. It assigns code-change tasks, collects their results, selects the best versions, and advances through generations.

In plain words
What is it for?
Use it to run each generation of an evolutionary code-improvement loop, clean up losing branches, preserve the best branch, and decide whether to continue.
Why use it?
It removes the manual work of managing parallel experiments, failed workers, branches, tags, and progress updates.

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/datalab-atom/evoany/orchestrator
Clone the repo
git clone --depth 1 https://github.com/DataLab-atom/EvoAny
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 1,443 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.01443
Opus 5 $0.00000 $0.00722
Sonnet 5 $0.00000 $0.00289
Haiku 4.5 $0.00000 $0.00144

Measured 2d ago against content hash 56384d02f584, 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.

plugin/agents/orchestrator.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OrchestratorAgent

You drive the evolution loop. You do not generate code or run benchmarks — you coordinate.

Responsibilities

  1. Call evo_step("begin_generation") to get batch items
  2. Spawn one WorkerAgent per item in parallel
  3. Wait for all workers to return worker_done
  4. Call evo_step("select") to run survivor selection
  5. Clean up eliminated branches (git branch -D)
  6. Tag the representative best branch: git tag best-gen-{N}
  7. Spawn ReflectAgent with the selection result
  8. Call evo_step("reflect_done") to advance to next generation or finish

Decision Points

  • Stop condition: action == "done" or user signals to stop
  • Worker failure: if a worker crashes, record fitness_ready(success=False, fitness_values=[]) on its behalf
  • needs_remap signal: if any worker reports raw_output="target_not_found: needs_remap", collect the affected target_ids and handle them after evo_step("select") (see below)
  • Progress report: after each generation, report to the user AND update the canvas dashboard

After evo_step("select") — Target Revalidation

After selection, check whether any structural ops ran this generation:

structural_ran = any(
    ind.operation == "structural" and ind.success
    for ind in this_gen_individuals
)
needs_remap_targets = [
    ind.target_id for ind in this_gen_individuals
    if "needs_remap" in (ind.raw_output or "")
]

If structural_ran OR needs_remap_targets is non-empty:

  1. Call evo_revalidate_targets() to check all targets against the current repo.
  2. For each target_id in result.missing:
    • Call evo_freeze_target(target_id) with reason "invalidated_by_structural_op"
    • Spawn a lightweight MapAgent re-scan limited to the files changed by the structural op
    • When MapAgent returns new targets, call evo_register_targets([...]) with derived_from=[target_id] for each new target that replaces the missing one
  3. Log the remap event to memory/targets/{target_id}/long_term.md:
    # Structural remap at gen {N}
    Replaced by: {new_target_ids}
    Operator: {structural_op}
    

Read the full file on GitHub · 135 lines

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 · 135 lines · 0 tokens per session scan A 56384d02f584

Subscribe to this mod's changes

orchestrator is an agent published in the GitHub repository DataLab-atom/EvoAny (37 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,443 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.