open-orchestrator-cheap

Orchestrates open-weight models by routing tasks to the cheapest model that fits the context window.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running multi-agent coding workflows on frontier models is expensive, and routing tasks to oversized models wastes money while undersized models compact mid-task and lose state. This Skill defines a cost-optimized orchestration structure where an orchestrator delegates pre-digested work slices to cheap worker models and reserves expensive models for planning and validation gates. ## Core Features & Use Cases - Three-role architecture: GLM-5.2 acts as the oracle for planning and validation gates, mimo-v2.5-pro coordinates as the orchestrator, and mimo-v2.5 or deepseek-v4-flash execute bounded edits as workers. - Context-based routing: Measures the exact working set with wc -l and routes each task to the cheapest model whose window holds it under 75% utilization, with a return contract (out_of_scope, too_big, mismatch) that triggers re-routing instead of silent compaction. - Hard delegation rule: The orchestrator never edits files itself; every code change goes through a worker with a scoped prompt containing exact files, one precise task, and a success check. - Use Case: When refactoring a large codebase on a budget, the orchestrator greps and measures the affected files, splits the work into slices under 240K tokens, spawns parallel mimo-v2.5 workers, and calls GLM-5.2 once at the end to validate coherence. ## Quick Start Ask the agent to orchestrate this refactoring task using cheap open models, delegating all edits to workers and validating the result with the oracle.

Frequently Asked Questions about open-orchestrator-cheap

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

FAQPage Schema
How do I reduce costs when running multi-agent coding workflows?

Route each task to the cheapest model whose context window holds the working set under 75% utilization. Measure the exact files with wc -l before routing, delegate edits to cheap workers like mimo-v2.5, and reserve expensive models like GLM-5.2 for one validation gate per task.

How to choose between mimo-v2.5 and deepseek-v4-flash for coding tasks?

Both models cost the same, so choose by context window. Use mimo-v2.5 for tasks with a working set under roughly 240K tokens, and deepseek-v4-flash when only its 1M token window can hold the sweep in one pass.

Why does a worker model get slow and lose context mid-task?

The task exceeded the model's context budget, triggering auto-compaction that discards state and forces re-reading. Prevent this by measuring the working set first, keeping utilization under 75%, and splitting oversized tasks into bounded slices.

When should the orchestrator call the oracle model?

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 since GLM-5.2 costs 5 to 15 times more than the other models.

Can the orchestrator model edit files directly for small fixes?

No, the orchestrator never writes code, even for one-line fixes. Every edit goes through a worker with a scoped prompt containing exact files, one precise task, and a success check, because direct edits are the failure mode this structure prevents.