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-conventions - Prompt - OpenSmartRoute

Name: git-conventions
Author: bernierllc

Prompt file imported from bernierllc/agents-environment-config (.cursor/commands/skills/git-conventions.md). Copyright stays with the author.

Git conventions

One rule, enforced where the commit happens: the first line of every commit is type(scope): lowercase description.

types: feat fix docs chore test refactor perf ci build revert release style
scope: optional, [a-z0-9._/,-]+ (fix(senders,campaigns): is fine), ! before the colon for breaking changes
description: starts with a lowercase letter or a digit; anything after that is free, so GitHub's squash suffix (#815) passes
passthrough: Merge …, Revert "…", fixup! …, squash! …, amend! … are git's own subjects and are not checked

Install

aec install skill git-conventions

hooks.json carries a git override for commit-msg. aec writes it as a delimited block into the repo's active hooks directory (.husky/ if present, else core.hooksPath, else .git/hooks), so it runs in every worktree of that repo. The block runs in a subshell, so a passing subject falls through to whatever else the hook file runs (husky lines, other aec blocks). The check is inline in the hook, so it works in worktrees where .claude/skills/ is gitignored and absent.

Verify

sh "$(aec info skill git-conventions --path 2>/dev/null || echo .claude/skills/git-conventions)/scripts/selftest.sh"

or by hand: git commit --allow-empty -m 'Bad Subject' is rejected, git commit --allow-empty -m 'chore(hooks): check the hook (#1)' passes (then git reset --hard HEAD~1).

Why a hook, not commitlint

The global rules said "Commitlint enforces it." Nothing did: no repo had commitlint, husky or a commit-msg hook. A dependency-free hook that aec installs is the smallest thing that is true in every repo, including ones with no package.json.

Install git-conventions 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": "# Git conventions\n\nOne rule, enforced where the commit happens: the first line of every commit is\n`type(scope): lowercase description`.\n\n- **types:** `feat fix docs chore test refactor perf ci build revert release style`\n- **scope:** optional, `[a-z0-9._/,-]+` (`fix(senders,campaigns):` is fine), `!` before the colon for breaking changes\n- **description:** starts with a lowercase letter or a digit; anything after that is free, so GitHub's squash suffix `(#815)` passes\n- **passthrough:** `Merge …`, `Revert \"…\"`, `fixup! …`, `squash! …`, `amend! …` are git's own subjects and are not checked\n\n## Install\n\n```\naec install skill git-conventions\n```\n\n`hooks.json` carries a `git` override for `commit-msg`. aec writes it as a delimited block into\nthe repo's active hooks directory (`.husky/` if present, else `core.hooksPath`, else `.git/hooks`),\nso it runs in every worktree of that repo. The block runs in a subshell, so a passing subject falls through to whatever else the hook file runs (husky lines, other aec blocks). The check is inline in the hook, so it works in\nworktrees where `.claude/skills/` is gitignored and absent.\n\n## Verify\n\n```\nsh \"$(aec info skill git-conventions --path 2>/dev/null || echo .claude/skills/git-conventions)/scripts/selftest.sh\"\n```\n\nor by hand: `git commit --allow-empty -m 'Bad Subject'` is rejected, `git commit --allow-empty -m 'chore(hooks): check the hook (#1)'` passes (then `git reset --hard HEAD~1`).\n\n## Why a hook, not commitlint\n\nThe global rules said \"Commitlint enforces it.\" Nothing did: no repo had commitlint, husky or a\n`commit-msg` hook. A dependency-free hook that aec installs is the smallest thing that is true\nin every repo, including ones with no `package.json`.", "variables": [], "notes": "Use when committing in a repo that requires lowercase conventional commits, or when a commit is rejected with `commit-msg: subject must be`. Enforces conventional commits with a lowercase subject (`type(scope): description`) through a git commit-msg hook that aec installs into the repo's active hooks directory, so no commitlint install is needed.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/bernierllc/agents-environment-config", "path": ".cursor/commands/skills/git-conventions.md", "ref": "270dd451fc65428ecc2af6feb37f8ae875ca8e02", "url": "https://github.com/bernierllc/agents-environment-config/blob/270dd451fc65428ecc2af6feb37f8ae875ca8e02/.cursor/commands/skills/git-conventions.md", "key": "bernierllc/agents-environment-config/.cursor/commands/skills/git-conventions.md" } } }

git-conventions

About

Git conventions

Install

Verify

Why a hook, not commitlint

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