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.

opencode - Skill - OpenSmartRoute

Name: opencode
Author: xeon826

Imported from xeon826/dotfiles (opencode/AGENTS.md). Install upstream with npx skills add xeon826/dotfiles --skill opencode. Copyright stays with the author.

When a project's rules change, update its AGENTS.md — extend existing sections where possible, prune what becomes stale, and don't append narration of routine code changes (commit messages cover that).

Never git commit or git push on your own initiative — in any repo, including when a project's workflow (CI-on-merge, PR flow) makes it convenient. Prepare the changes, leave the branch/working tree ready, and tell the user it's ready; only commit or push when they explicitly ask in that request. Project conventions about commit style apply only once the user has asked for the commit.

DRY — "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system" (Hunt & Thomas, The Pragmatic Programmer)

Apply DRY broadly — not just code (dedupe via functions/abstractions) but database schemas, test plans, build systems, and documentation too. Prefer abstractions that are unlikely to change, or normalize data so redundancy never exists. Done right, changing one element never requires touching logically unrelated elements, and related elements change predictably and stay in sync. When you find yourself copy-pasting knowledge across files, extract it to its single authoritative source instead.

Try to refrain from using insider lingo when talking about finances.

The google-ads MCP server is FGRibreau/mcp-google-ads (Rust; rebuild at ~/git_clones/mcp-google-ads with cargo build --release after pulling). It targets Google Ads account 4666587905 (GiveMeAJob) with direct OAuth access — no GOOGLE_ADS_LOGIN_CUSTOMER_ID needed. Since the 2026-09-09 developer-token sunset, the API does not validate the developer-token header: GOOGLE_ADS_DEVELOPER_TOKEN in ~/.zsh_api_keys is an inert placeholder, and API access level is tied to the dan-marketing-mcp-01 Google Cloud project (Test level; Explorer application pending). Auth uses the authorized-user ADC at ~/.config/google-ads/user-adc.json, split into ~/.mcp-google-ads/credentials.json (installed OAuth-client format) and ~/.mcp-google-ads/token.json (refresh token) — the server requires both. API versions ≤v22 are blocked; the server defaults to v25 (GOOGLE_ADS_API_BASE_URL overrides). The manager account Dan API MCC (917-819-2119) exists only as a container; its API Center form handles just the App Conversion Tracking API. google-ads-official is the official uvx google-ads-mcp and uses the ADC directly. Querying production accounts additionally requires the account to allow it.

Install opencode 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": "xeon826-dotfiles-opencode", "kind": "skill", "name": "opencode", "description": "When a project's rules change, update its AGENTS.md — extend existing sections where possible, prune what becomes stale, and don't append narration of routine code changes (commit messages cover that).", "publisher": "xeon826", "version": "1.0.0", "capabilities": { "domains": [ "coding", "math" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "When a project's rules change, update its AGENTS.md — extend existing sections where possible, prune what becomes stale, and don't append narration of routine code changes (commit messages cover that)." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/xeon826/dotfiles", "path": "opencode/AGENTS.md", "ref": "6416a00d7982b320e43041c792ccf724502fd96f", "url": "https://github.com/xeon826/dotfiles/blob/6416a00d7982b320e43041c792ccf724502fd96f/opencode/AGENTS.md", "key": "xeon826/dotfiles/opencode/AGENTS.md" } }, "instructions": "When a project's rules change, update its AGENTS.md — extend existing sections where possible, prune what becomes stale, and don't append narration of routine code changes (commit messages cover that).\n\nNever `git commit` or `git push` on your own initiative — in any repo, including when a project's workflow (CI-on-merge, PR flow) makes it convenient. Prepare the changes, leave the branch/working tree ready, and tell the user it's ready; only commit or push when they explicitly ask in that request. Project conventions about commit style apply only once the user has asked for the commit.\n\n## DR", "cost": { "context_tokens": 632 } }

opencode

About

DRY — "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system" (Hunt & Thomas, The Pragmatic Programmer)

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