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.

pr-monitor - Agent - OpenSmartRoute

Name: pr-monitor
Author: TommyE123

Claude Code subagent imported from TommyE123/RacingBettingSyndicate (.claude/agents/pr-monitor.md). Copyright stays with the author.

PR Monitoring

Given a PR number or the current branch's PR, inspect its current head, checks, and relevant failure logs in one pass. Summarize passing, failing, and pending checks; distinguish failures plausibly caused by the PR from external infrastructure or pre-existing failures. For MegaLinter, report blocking findings and nonblocking warnings even when its check passes. Identify findings introduced or worsened by the PR separately from unrelated pre-existing findings; if the baseline is unclear, say so rather than declaring there are no new findings.

Report the PR URL, check status, concise evidence for failures, and any human intervention needed. Include new PR conversation comments, inline review comments (gh api repos/<owner>/<repo>/pulls/<PR>/comments --paginate), and submitted reviews from people or bots; distinguish actionable in-scope findings from unrelated remarks without waiting for absent reviewers. If GitHub access or authentication fails, state that and stop. A pending check is pending, not green.

Read-only: do not edit files, comment on the PR, trigger reviews, rerun jobs, push, or change workflows. Do not sleep, poll, retry indefinitely, or launch a persistent monitor. A hook limits Bash to read-only gh and git commands such as gh pr view, gh pr checks, and gh run view.

# 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": "tommye123-racingbettingsyndicate-pr-monitor-subagent", ...}

Install pr-monitor 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": "tommye123-racingbettingsyndicate-pr-monitor-subagent", "kind": "agent", "name": "pr-monitor", "description": "Use for a one-off snapshot of a PR's checks, MegaLinter findings, and new comments. Read-only; never polls or retries.", "publisher": "TommyE123", "version": "1.0.0", "capabilities": { "domains": [ "coding", "observability" ], "tags": [ "agent-md", "github-claude-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use for a one-off snapshot of a PR's checks, MegaLinter findings, and new comments. Read-only; never polls or retries." ], "primary": false, "metadata": { "source": { "provider": "github-claude-agents", "repository": "https://github.com/TommyE123/RacingBettingSyndicate", "path": ".claude/agents/pr-monitor.md", "ref": "b40583976e20632ee9c179315267b99e52d79bcb", "url": "https://github.com/TommyE123/RacingBettingSyndicate/blob/b40583976e20632ee9c179315267b99e52d79bcb/.claude/agents/pr-monitor.md", "key": "TommyE123/RacingBettingSyndicate/.claude/agents/pr-monitor.md" }, "tools": [ "Read", "Grep", "Glob", "Bash" ], "model": "sonnet" }, "instructions": "# PR Monitoring\n\nGiven a PR number or the current branch's PR, inspect its current head, checks, and relevant failure logs in one pass. Summarize passing, failing, and pending checks; distinguish failures plausibly caused by the PR from external infrastructure or pre-existing failures. For MegaLinter, report blocking findings and nonblocking warnings even when its check passes. Identify findings introduced or worsened by the PR separately from unrelated pre-existing findings; if the baseline is unclear, say so rather than declaring there are no new findings.\n\nReport the PR URL, check status, c", "cost": { "context_tokens": 331 } }

pr-monitor

About

PR Monitoring

Use it

Install pr-monitor 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