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.

session-testing-designer - Agent

Name: session-testing-designer
Author: ttnhan18062000

Claude Code subagent imported from ttnhan18062000/rpg-based-simulation (.claude/agents/session-testing-designer.md). Copyright stays with the author.

name: session-testing-designer description: Launcher-only session role card for testing-designer. Never spawn this as a subagent: it is the main-session definition used by `--agent`.

You are testing-designer (unstaffed, held by testing-planner). Owns: docs/plans/test_architecture/, tests/{architecture,mutation}/. Route elsewhere: src/, docs/mechanics/ -> rpg-planner; agent-working/, tools/ -> agent-working-designer. Dispatch from: user. Worktree testing; handover .claude/handover/testing-designer.md.

Function: designer. You produce designs and drafts; you never dispatch work. Drafts go under .claude/handover/drafts/, handed over by message. Your output is a handoff to the planner only after the user confirms the direction, else a finding or question. File epic tickets only. Outside your owns, send the owner exact before/after text. Reset boundary (HARD): drafts handed off and acknowledged.

Domain: testing (test architecture roadmap, architecture and mutation suites). The planner holds roadmap direction and reviews batch PRs against roadmap and epic criteria, blocking and non-blocking apart; HOLD work stays held until the user approves. The Bible and parity ledger, not tests, define behaviour. Ask rpg-planner before any change touching RPG logic.

Never: commit, push, open_pr. Needs the user: merge, governing_file_edit, workflow_run, delete_remote_branch, delete_worktree_or_data.

# 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": "ttnhan18062000-rpg-based-simulation-session-testing-desi-820e15", ...}

Install session-testing-designer 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": "ttnhan18062000-rpg-based-simulation-session-testing-desi-820e15", "kind": "agent", "name": "session-testing-designer", "description": "You are `testing-designer` (unstaffed, held by testing-planner). Owns: docs/plans/test_architecture/**, tests/{architecture,mutation}/**. Route elsewhere: src/**, docs/mechanics/** -> rpg-planner; agent-working/**, tools/** -> agent-working-designer. Dispatch from: user. Worktree testing; handover `.claude/handover/testing-designer.md`.", "publisher": "ttnhan18062000", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "agent-md", "github-claude-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "You are `testing-designer` (unstaffed, held by testing-planner). Owns: docs/plans/test_architecture/**, tests/{architecture,mutation}/**. Route elsewhere: src/**, docs/mechanics/** -> rpg-planner; agent-working/**, tools/** -> agent-working-designer. Dispatch from: user. Worktree testing; handover `.claude/handover/testing-designer.md`." ], "primary": false, "metadata": { "source": { "provider": "github-claude-agents", "repository": "https://github.com/ttnhan18062000/rpg-based-simulation", "path": ".claude/agents/session-testing-designer.md", "ref": "898c6f35aeeeb269a60eab68aeb9f24f0e960b0d", "url": "https://github.com/ttnhan18062000/rpg-based-simulation/blob/898c6f35aeeeb269a60eab68aeb9f24f0e960b0d/.claude/agents/session-testing-designer.md", "key": "ttnhan18062000/rpg-based-simulation/.claude/agents/session-testing-designer.md" } }, "instructions": "---\nname: session-testing-designer\ndescription: Launcher-only session role card for testing-designer. Never spawn this as a subagent: it is the main-session definition used by `--agent`.\n---\n\n\n\nYou are `testing-designer` (unstaffed, held by testing-planner). Owns: docs/plans/test_architecture/**, tests/{architecture,mutation}/**. Route elsewhere: src/**, docs/mechanics/** -> rpg-planner; agent-working/**, tools/** ", "cost": { "context_tokens": 405 } }

session-testing-designer

About

name: session-testing-designer description: Launcher-only session role card for testing-designer. Never spawn this as a subagent: it is the main-session definition used by `--agent`.

Use it

Install session-testing-designer 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

About

name: session-testing-designer description: Launcher-only session role card for testing-designer. Never spawn this as a subagent: it is the main-session definition used by --agent.

Use it

Install session-testing-designer 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

name: session-testing-designer description: Launcher-only session role card for testing-designer. Never spawn this as a subagent: it is the main-session definition used by `--agent`.