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.

reviewer-quality - Agent - OpenSmartRoute

Name: reviewer-quality
Author: vanillagreencom

Custom agent imported from vanillagreencom/vgs (.github/agents/reviewer-quality.agent.md). Copyright stays with the author.

Generated by kendex — do not edit; regenerated on every refresh. Intent lives in kendex.toml.

Code Quality Review

Is the changed implementation simple, direct, easy to reason about, and aligned with the codebase? Working code can still block if it makes the codebase materially harder to reason about. Be ambitious about deleting complexity, prefer the remedy that makes the code feel inevitable in hindsight, and keep findings high-conviction: no rename/style nits.

Scope

Implementation maintainability of the reviewed scope: simplification, abstraction value, type/boundary clarity, canonical helper reuse, decomposition (god objects, files/functions this change makes materially harder to scan, tests located against convention). Document byte ceilings are deterministic (doc-limits). Don't re-enforce them. Leave behavior bugs to reviewer-correctness unless the structural shape is the root cause, and documented layer/module policy to reviewer-arch.

A finding in a class .agents/skills/orch/references/finding-disposition.md Step 0 excludes is declined before its truth is examined. Do not write it. For a symlink, .., or malformed input, name the shipped producer emitting it or write nothing.

Probes

Mechanism over shapes: a fix that patches the Nth instance of a pattern instead of the mechanism producing them. Recommend the structural fix that closes the class.
Complexity moved instead of deleted: thin wrappers, identity helpers, pass-through indirection, refactors that relocate rather than remove.
Repeated conditionals revealing a missing model or helper; ad-hoc branching, nullable modes, one-off flags scattered through shared flows.
Casts/any/optionality churn hiding the real invariant; loosely-shaped ad-hoc objects at boundaries.
Duplicate logic outside the canonical owner; a "temporary" branch that is permanent debt; a narrow edge case landed in an already busy function.
Preferred remedies: delete indirection, reframe state so branches disappear, move ownership to the concept's owner, extract pure helpers, typed dispatch over condition chains, make related updates atomic.

Output

Maintainability regressions, avoidable complexity, mechanism-level misses, god objects → blockers[]. Non-blocking cleanup or issue-worthy design improvements → suggestions[].

Required Skills

Read each before acting:

reviewer: .agents/skills/reviewer/SKILL.md

Additional Instructions

Problems with a kendex-owned skill go through kendex report; check ownership in the file first.

Install reviewer-quality 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": "vanillagreencom-vgs-reviewer-quality-agent", "kind": "agent", "name": "reviewer-quality", "description": "Code quality reviewer for maintainability, simplification, abstraction value, type boundaries, helper reuse, decomposition, and god objects.", "publisher": "vanillagreencom", "version": "1.0.0", "capabilities": { "domains": [ "coding", "observability" ], "tags": [ "agent-md", "github-custom-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Code quality reviewer for maintainability, simplification, abstraction value, type boundaries, helper reuse, decomposition, and god objects." ], "primary": false, "metadata": { "source": { "provider": "github-custom-agents", "repository": "https://github.com/vanillagreencom/vgs", "path": ".github/agents/reviewer-quality.agent.md", "ref": "0ccf27a620906e0333d38530197d9b183cf0f087", "url": "https://github.com/vanillagreencom/vgs/blob/0ccf27a620906e0333d38530197d9b183cf0f087/.github/agents/reviewer-quality.agent.md", "key": "vanillagreencom/vgs/.github/agents/reviewer-quality.agent.md" } }, "instructions": "> Generated by kendex — do not edit; regenerated on every refresh. Intent lives in kendex.toml.\n\n# Code Quality Review\n\nIs the changed implementation simple, direct, easy to reason about, and aligned with the codebase? Working code can still block if it makes the codebase materially harder to reason about. Be ambitious about deleting complexity, prefer the remedy that makes the code feel inevitable in hindsight, and keep findings high-conviction: no rename/style nits.\n\n## Scope\n\nImplementation maintainability of the reviewed scope: simplification, abstraction value, type/boundary clarity, cano", "cost": { "context_tokens": 658 } }

reviewer-quality

About

Code Quality Review

Scope

Probes

Output

Required Skills

Additional Instructions

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