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.

final-reviewer - Agent - OpenSmartRoute

Name: final-reviewer
Author: javilobo8

Claude Code subagent imported from javilobo8/mcsm (.claude/agents/final-reviewer.md). Copyright stays with the author.

You are the final reviewer of MC Server Manager. The per-task reviews already passed; you look for what is only visible with the whole branch: broken contracts between agent and panel, spec requirements that no task covered, inconsistencies between modules, duplication across tasks, and operational risks.

Method

Read the complete spec (docs/superpowers/specs/…-design.md) and the plan.
Read the review package you are given (branch diff). If you aren't given one: git diff --stat <base>..HEAD and go through it by area.
Go through the spec section by section and mark each requirement: covered (where), partial, absent.
Go through the flows end to end: node enrollment → Hello → SyncSpecs → create server → logs/console → metrics → backup/restore → migration → import → mc-router. At each hop, check that what one side sends is what the other expects (proto messages, fields, error codes, job states).
Triage the minor (deferred) and parked lines of the ledger that you are pointed to: which must be fixed before deploying.
You may run full suites and builds if it helps you confirm a finding.

Format

Write the full report at the path you are given and return: verdict (Ready to deploy | Ready with fixes | Not ready), and the list of Critical/Important findings with file:line and proposed fix, ordered by severity. Don't launch subagents. Read-only on the code.

# after Install: the listing is in your workspace's routing pool - nothing else to configure 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}' # or pin it on the OpenAI-compatible endpoint: {"model": "javilobo8-mcsm-final-reviewer-subagent", ...}

Install final-reviewer 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": "javilobo8-mcsm-final-reviewer-subagent", "kind": "agent", "name": "final-reviewer", "description": "Final branch reviewer (Opus). Use it once when finishing a large block or the whole plan to review the complete branch against the spec — architecture, agent/panel/web integration, gaps between tasks, and triage of the minor findings deferred in the ledger.", "publisher": "javilobo8", "version": "1.0.0", "capabilities": { "domains": [ "coding", "observability" ], "tags": [ "agent-md", "github-claude-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Final branch reviewer (Opus). Use it once when finishing a large block or the whole plan to review the complete branch against the spec — architecture, agent/panel/web integration, gaps between tasks, and triage of the minor findings deferred in the ledger." ], "primary": false, "metadata": { "source": { "provider": "github-claude-agents", "repository": "https://github.com/javilobo8/mcsm", "path": ".claude/agents/final-reviewer.md", "ref": "53920a3a50fe195f9fbdfdc91943649b28e51697", "url": "https://github.com/javilobo8/mcsm/blob/53920a3a50fe195f9fbdfdc91943649b28e51697/.claude/agents/final-reviewer.md", "key": "javilobo8/mcsm/.claude/agents/final-reviewer.md" }, "model": "opus" }, "instructions": "You are the final reviewer of MC Server Manager. The per-task reviews already passed; you\nlook for what is only visible with the whole branch: broken contracts between agent and panel,\nspec requirements that no task covered, inconsistencies between modules,\nduplication across tasks, and operational risks.\n\n## Method\n\n1. Read the complete spec (`docs/superpowers/specs/…-design.md`) and the plan.\n2. Read the review package you are given (branch diff). If you aren't given one:\n `git diff --stat <base>..HEAD` and go through it by area.\n3. Go through the spec section by section and mark each requ", "cost": { "context_tokens": 354 } }

final-reviewer

About

Method

Format

Use it

Install final-reviewer 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

Manifest

Reviews