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.

agent - Skill - OpenSmartRoute

Name: agent
Author: samzong

Imported from samzong/Rx (agent/AGENTS.md). Install upstream with npx skills add samzong/Rx --skill agent. Copyright stays with the author.

Rx Agent Product Quality Standard

Rx is both the product and its own developer. Develop it as a world-class, production-grade open-source application and as the user's primary agent and interface to the outside world.

User-visible quality is non-negotiable. UX and DX are a release boundary, not polish. The product must feel unified, restrained, refined, ordered, fast, and trustworthy from its first interaction. Eliminate cheapness, patchwork, staticness, and feature-accumulation artifacts.

Favor a small number of high-value, real user workflows over feature volume. Do not add a capability unless it materially improves a clear primary path.
Build one coherent system: information architecture, terminology, interaction patterns, states, errors, shortcuts, typography, spacing, color, and motion must agree.
Use progressive disclosure. Make the safe default reliable, the novice path understandable, and expert workflows increasingly fast.
Make execution observable. Loading, streaming, tool execution, waiting for approval, success, cancellation, and failure must have prompt, accurate, comprehensible feedback. Never make users guess what Rx is doing.
Treat DX as product UX: installation, configuration, CLI output, help, examples, errors, logs, upgrades, recovery, and automation must be designed with the same care as interactive surfaces.
Treat performance and reliability as user experience: startup, time to first useful response, responsiveness, long-running task progress, failure recovery, and graceful degradation are primary-path requirements.
Ship open source with product completeness: reproducible builds, accurate documentation, clear contribution paths, explicit licenses, and strong security boundaries. Open source is never an excuse for a rough experience.
Earn repeated use through usefulness, fluency, trust, and user control, never through dark patterns, deceptive urgency, manipulative notifications, or engineered dependency.
Verify the full experience, not only code correctness. Review first-run, normal, empty, loading, streaming, error, cancellation, recovery, upgrade, accessibility, and edge-case paths appropriate to every user-visible change.

Do not mistake premium quality for decorative complexity. Premium quality means users immediately understand what to do, always understand what is happening, retain control when something fails, and become faster with continued use.

For every Rx change, assess three layers:

Core experience: first run, provider configuration, model selection, task execution, tool approval, streamed output, errors, and task recovery form a low-friction coherent path.
Agent behavior: plans, progress, risks, approval requests, and final reports are concise, accurate, structured, and free of performative noise.
Engineering gate: user-visible changes require consistency review, real-path validation, and applicable project checks. Passing tests alone does not make a change ready to ship.

Install agent 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.

{ "ocm": "1", "id": "samzong-rx-agent", "kind": "skill", "name": "agent", "description": "Rx is both the product and its own developer. Develop it as a world-class, production-grade open-source application and as the user's primary agent and interface to the outside world.", "publisher": "samzong", "version": "1.0.0", "capabilities": { "domains": [ "coding", "observability" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Rx is both the product and its own developer. Develop it as a world-class, production-grade open-source application and as the user's primary agent and interface to the outside world." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/samzong/Rx", "path": "agent/AGENTS.md", "ref": "82a515899d23f4ee4e490c503402f25c11385d92", "url": "https://github.com/samzong/Rx/blob/82a515899d23f4ee4e490c503402f25c11385d92/agent/AGENTS.md", "key": "samzong/Rx/agent/AGENTS.md" } }, "instructions": "# Rx Agent Product Quality Standard\n\nRx is both the product and its own developer. Develop it as a world-class,\nproduction-grade open-source application and as the user's primary agent and\ninterface to the outside world.\n\nUser-visible quality is non-negotiable. UX and DX are a release boundary, not\npolish. The product must feel unified, restrained, refined, ordered, fast, and\ntrustworthy from its first interaction. Eliminate cheapness, patchwork,\nstaticness, and feature-accumulation artifacts.\n\n- Favor a small number of high-value, real user workflows over feature volume.\n Do not add a capabi", "cost": { "context_tokens": 759 } }

agent

About

Rx Agent Product Quality Standard

Install agent 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