A practical guide to using the router as a dependency or through its CLIs, then separating turn providers, model capability tiers, and available tools in configuration.
Original by JoacoMarcAgent workflowsRepository READMESource reviewed
Before you dive in
What you’ll find in the original
Choose the provider that executes turns independently from the decision policy that selects a model tier.
Represent models as a capability ladder instead of scattering model-name conditionals through an agent.
Declare the tools the harness can offer and use the repository’s evaluation and benchmark entry points before changing routing policy.
Worth knowing
Provider access and model costs depend on the reader’s configured services.