How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

templates - Skill - OpenSmartRoute

Imported from lilycandoit/lily-ai-workflows (templates/AGENTS.md). Install upstream with npx skills add lilycandoit/lily-ai-workflows --skill templates. Copyright stays with the author.

Project Instructions

This project uses Lily AI Workflows with Codex.

Reusable workflows are installed at:

~/.codex/custom-workflows/

Codex skill shortcuts are installed at:

~/.codex/skills/codex-*

Project-specific source of truth lives in:

.planning/

Before Work

Before planning or implementation, read:

~/.codex/custom-workflows/planning-system.md
.planning/STATE.md
.planning/ROADMAP.md
the relevant phase folder under .planning/phases/
the target plan file, if executing work

Do not rely on chat history when project files contain the answer.

Common Shortcuts

codex-progress — check current project state
codex-next — move to the next phase when ready
codex-plan — create a focused plan
codex-plan-check — optional plan review saved beside the plan
codex-execute — execute one plan
codex-verify — verify completed work
codex-commit — create a local git checkpoint
codex-recap — summarize project state from files
codex-consult — strategic consultation before planning or implementation
codex-test-plan — decide unit, integration, E2E, and manual testing strategy
codex-add-tests — add missing automated tests
codex-uat — create or record User Acceptance Testing checks

Rules

Keep project memory in .planning/.
Execute one plan at a time.
Treat the matching plan-check file as optional context; if present, read it before execution.
Write the matching summary file after completing a plan.
Update .planning/STATE.md after meaningful progress using the installed planning-system State File Convention. Keep current phase folder, phase title, current plan, status, resume file, blockers, and next action explicit.
Always create new phase folders with the canonical name pattern phase-{number}-{short-summary} under .planning/phases/.
Use lowercase, hyphen-separated words; examples: phase-1-foundation, phase-2-authentication-user-roles.
Keep the folder stable once created and make the slug descriptive enough to spot the feature or fix by directory name alone.
Do not push unless explicitly asked.

Install templates and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

templates

About

Project Instructions

Before Work

Common Shortcuts

Rules

Install templates and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews