orchestrator

Dispatch prompts to local or cheap LLMs with auto-routing and health checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/isndotbiz/ged --skill orchestrator-isndotbiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/isndotbiz/ged/tree/main/.claude/skills/orchestrator
Command: npx skills add https://github.com/isndotbiz/ged --skill orchestrator-isndotbiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch prompts to local/cheap LLMs via the orchestrator to avoid expensive Claude subagent calls and reduce operational costs.

Core Features & Use Cases

  • Route prompts to cheap/local LLMs (GLM, TabbyAPI, OpenRouter, CLI agents) to minimize Claude usage.
  • Auto-dispatch and swarm capabilities to gather multiple perspectives and improve result quality.
  • Health checks and spend tracking to inform decision-making and budgeting.

Quick Start

Dispatch a prompt to the best available worker using the orchestrator.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I route prompts to local LLMs to reduce Claude usage costs?

To reduce Claude usage costs, you can dispatch prompts to local or cheap LLMs using an orchestrator that auto-routes tasks to the best available workers, cutting operational spend.

What is LLM prompt routing and how does it help with cost savings?

LLM prompt routing dispatches tasks to cheaper local models or external workers instead of expensive subagents, tracking spend and applying health checks to minimize operational costs.

Can I use auto-dispatch and swarm capabilities for code review tasks?

Yes, you can use auto-dispatch and swarm capabilities to gather multiple perspectives for code review, generation, research, and validation tasks by routing prompts to available workers.

How do I track LLM spend and monitor health checks for local workers?

You can track LLM spend and monitor worker availability by querying the health and spend endpoints, which inform budgeting decisions and check the status of routed tasks.

Does this prompt dispatch approach work with OpenRouter and CLI agents?

Yes, the prompt dispatch approach works with OpenRouter, CLI agents, GLM, and TabbyAPI, routing prompts to these workers to minimize expensive Claude subagent calls.

What are the limitations of routing prompts to cheap LLMs?

Routing prompts to cheap LLMs limits result quality compared to expensive subagents, though auto-dispatch and swarm capabilities help gather multiple perspectives to improve outputs.