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.

work-ticket - Prompt - OpenSmartRoute

Name: work-ticket
Author: kayleschmoyer

Prompt file imported from kayleschmoyer/Legacy (.codex/prompts/work-ticket.md). Fill in {{arguments}} before use. Copyright stays with the author.

You are the chief operator for Jira ticket {{arguments}}: orient on the full ticket, route it to the right mode, delegate or execute, verify against the ACs, and hand off at merged — not before.

First and only directive: load the skill with .agents/skills/work-ticket/SKILL.md immediately, before any other tool call. Do not invoke the Skill tool with work-ticket — that name resolves back to this command file, not the skill (see .agents/skills/mcp-first/references/diagnostics.md#skill-tool-returns-this-command-instead-of-skillmd-content-ls-8719). The skill is the authoritative procedure — it owns orientation (full-ticket read, AC quote-back) and mode routing, and its references/ own execution (leaf-mode, dispatch-modes, enrich-ticket). Follow every step in order and complete every item in the checklists it creates. Do not paraphrase, summarize, or substitute steps.

Specific invocation: /work-ticket LS-3421 — always pass the ticket key directly, not a description.

You are the **chief operator** for Jira ticket **{{arguments}}**: orient on the full ticket, route it to the right mode, delegate or execute, verify against the ACs, and hand off at merged — not before. **First and only directive:** load the skill with `.agents/skills/work-ticket/SKILL.md` immediately, before any other tool call. Do not invoke the `Skill` tool with `work-ticket` — that name resolves back to this command file, not the skill (see `.agents/skills/mcp-first/references/diagnostics.md#skill-tool-returns-this-command-instead-of-skillmd-content-ls-8719`). The skill is the authoritative procedure — it owns orientation (full-ticket read, AC quote-back) and mode routing, and its `references/` own execution (leaf-mode, dispatch-modes, enrich-ticket). Follow every step in order and complete every item in the checklists it creates. Do not paraphrase, summarize, or substitute steps. > Specific invocation: `/work-ticket LS-3421` — always pass the ticket key directly, not a description.

Install work-ticket 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.

{ "prompt": "\n\nYou are the **chief operator** for Jira ticket **{{arguments}}**: orient on the full ticket, route it to the right mode, delegate or execute, verify against the ACs, and hand off at merged — not before.\n\n**First and only directive:** load the skill with `.agents/skills/work-ticket/SKILL.md` immediately, before any other tool call. Do not invoke the `Skill` tool with `work-ticket` — that name resolves back to this command file, not the skill (see `.agents/skills/mcp-first/references/diagnostics.md#skill-tool-returns-this-command-instead-of-skillmd-content-ls-8719`). The skill is the authoritative procedure — it owns orientation (full-ticket read, AC quote-back) and mode routing, and its `references/` own execution (leaf-mode, dispatch-modes, enrich-ticket). Follow every step in order and complete every item in the checklists it creates. Do not paraphrase, summarize, or substitute steps.\n\n> Specific invocation: `/work-ticket LS-3421` — always pass the ticket key directly, not a description.", "variables": [ "arguments" ], "notes": "Use when given a Jira ticket key to implement end-to-end: code, PR, and merge. Arguments: LS-####.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/kayleschmoyer/Legacy", "path": ".codex/prompts/work-ticket.md", "ref": "5b9fc8984c3d0586e2385db8de07cb703c401191", "url": "https://github.com/kayleschmoyer/Legacy/blob/5b9fc8984c3d0586e2385db8de07cb703c401191/.codex/prompts/work-ticket.md", "key": "kayleschmoyer/Legacy/.codex/prompts/work-ticket.md" } } }

work-ticket

About

Use it

Install work-ticket 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

Manifest

Reviews