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.

git-commits - Skill - OpenSmartRoute

Instruction file imported from AsP3X/shroud (.cursor/rules/git-commits.mdc). Copyright stays with the author.

Git commits

Enforcement (strict)

This rule is mandatory for all agent-authored git actions in this repository.
If a git command would violate any section below, do not run it. Stop, explain the exact rule conflict, and ask for explicit user confirmation.

When commits are allowed

Create a git commit only when the user explicitly asks. Do not commit to "helpfully" save progress.
Do not git push, merge, rebase, or amend unless the user explicitly asks.

Branch model (this project)

Branch	Role
`master`	Root / release line. Stable, production-ready history.
`dev`	Integration branch. Collects completed work from feature branches.
`feature/<name>`	Feature development. Open from up-to-date `dev`.

Intended flow: feature/... → dev → master (via pull request).

Staging scope

Stage only paths the user named, or changes that clearly belong to the requested commit.
Before committing, run git status so staged vs unstaged is intentional.
When committing design changes, include iOS-App.pen and any assets it references (e.g. emoji/).

Safety (never commit)

Secrets: API keys, passwords, tokens, or full .env files.
Generated artifacts: target/, DerivedData/, *.xcarchive, node_modules/, etc. unless explicitly requested.

Commit message structure (required)

Every agent-authored commit message must begin with exactly one of:

TASK: — New work or refactors
FIX: — Regression from an earlier intentional change
BUGFIX: — Pre-existing incorrect behavior
DOCS: — Documentation-only changes
CHORE: — Tooling and maintenance only

Use a blank line before the body when more detail is needed. Merge/revert commits may use Git's default message.

Install git-commits 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.

git-commits

About

Git commits

Enforcement (strict)

When commits are allowed

Branch model (this project)

Staging scope

Safety (never commit)

Commit message structure (required)

Install git-commits 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