Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
codex - Skill - OpenSmartRoute
Skillv1.0.0
codex
When using Bash: - Prefer `fd` over `find` (e.g., `fd <pattern>` instead of `find . -name <pattern>`) - Prefer `rg` over `grep` (e.g., `rg <pattern> <path>` instead of `grep -r`) - Prefer `sd` over `s
Imported from ztlevi/dotty-config (misc/ai/codex/AGENTS.md). Install upstream with npx skills add ztlevi/dotty-config --skill codex. Copyright stays with the author.
CLI Tool Preferences
When using Bash:
Prefer fd over find (e.g., fd <pattern> instead of find . -name <pattern>)
Prefer rg over grep (e.g., rg <pattern> <path> instead of grep -r)
Prefer sd over sed (e.g., sd 'old' 'new' <file> instead of sed -i 's/old/new/g')
Still prioritize built-in tools (Read/Edit/Grep/Glob) over Bash where applicable.
Scuderia context
@~/dev/work/context/scuderia-context.md
CRUX / cr troubleshooting
@~/dev/work/context/crux-context.md
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install codex 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.
