open-orchestrator-medium

Orchestrates open-weight model workers with context-based routing and oracle validation gates.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill open-orchestrator-medium-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-orchestrator-medium
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/open-orchestrator-medium
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill open-orchestrator-medium-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-model AI work often wastes money on oversized models or fails when tasks exceed context windows. This Skill defines a medium-tier orchestration structure where GLM-5.2 coordinates and validates while cheaper mimo and deepseek variants execute bounded tasks, routing each slice to the cheapest model whose context window can hold it. ## Core Features & Use Cases - Role-based delegation: GLM-5.2 acts as orchestrator and oracle (in a fresh instance for unbiased gate validation), while mimo-v2.5/deepseek-v4-flash serve as cheap hands and mimo-v2.5-pro/deepseek-v4-pro as skilled hands. - Measurement-driven routing: Pre-flight working-set measurement (wc -l, ~10 tokens/line, <75% window target) determines whether a task goes to a 400K or 1M model, with a return contract (out_of_scope, too_big, mismatch) triggering re-routing instead of silent compaction. - Planned and unplanned modes with a context tripwire: Big tasks require a pre-built plan; unplanned exploration stops at ~50% context fill and demands a plan. - Use Case: Refactoring a module across 30 files — the orchestrator measures each slice, spawns parallel cheap-hand workers with exact file lists and success checks, then calls a fresh GLM-5.2 oracle at the end gate to validate coherence before review. ## Quick Start Ask the agent to orchestrate a multi-file code change using the open-orchestrator-medium tier, delegating edits to cheap workers and validating the result with an oracle gate.

Frequently Asked Questions about open-orchestrator-medium

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route tasks between cheap and skilled AI models?

Measure the working set with wc -l on the exact files in the worker's brief, estimate lines times ~10 tokens, and route to the cheapest model whose window holds it under 75%. Escalate to a skilled hand only with a stated reason the slice is not splittable.

How do I orchestrate multiple AI coding agents on one task?

Build a plan that pre-digests the work into bounded slices, then spawn one worker per slice with exact files, a single precise task, and a success check. The orchestrator never edits code itself; it supervises via periodic check-ins and integrates worker output.

What context window do mimo and deepseek models support?

The mimo-v2.5 and mimo-v2.5-pro variants support 400K tokens, while deepseek-v4-flash and deepseek-v4-pro support 1M tokens. GLM-5.2, used as orchestrator and oracle, also has a 1M window.

Why does a worker model get slow and inaccurate on large tasks?

When a task exceeds roughly 75% of the model's context window, mid-task auto-compaction kicks in, causing the worker to lose state, re-read files, and burn tokens. Split the task into smaller slices or escalate to a 1M-window model instead.

When should the orchestrator call the oracle for validation?

Call the oracle at deterministic gates: before validating completed work, after a plan is produced, when worker results conflict, or before irreversible changes. Budget one oracle call per task by default and batch pending questions into a single call.