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.

wicket - Skill - OpenSmartRoute

Name: wicket
Author: gaius-codius

Imported from gaius-codius/wicket (AGENTS.md). Install upstream with npx skills add gaius-codius/wicket. Copyright stays with the author.

Agent instructions

Read CONTRIBUTING.md for the toolchain, the checks to run before pushing, test rules, code style, and commit conventions. Those rules apply to agents too, including: no co-author, "generated with" or other tool attribution in commits or pull requests.

What to work on

Work is tracked in GitHub issues on the project board.

Epics are parent issues labelled type:epic. Work items are native sub-issues of an epic.
Types are labels, exactly one per issue: type:feature, type:research, type:bug, type:chore.
Order comes from native "blocked by" dependencies. Repo milestones group phases inside an epic.
Status and priority are fields on the board. Put every new issue on the board.
Pull requests say Closes #N so the issue closes and the board updates on merge.

Before starting an issue, check that nothing still blocks it. When you find a bug or chore while working, file it under the same epic with its own type label rather than widening the current change.

R=repos/gaius-codius/wicket
gh issue list --label type:epic --json number,title,state                    # open epics
gh api $R/issues/EPIC/sub_issues --jq '.[] | "#\(.number) \(.state) \(.title)"'  # what's left in an epic
gh api $R/issues/N/dependencies/blocked_by --jq '.[].number'                 # what blocks N
gh project item-list 3 --owner gaius-codius --format json                    # board status and priority

Go style

Lint must pass before you hand work back. Follow the go-style skill (gaius-codius/skills), which covers Effective Go, Go Code Review Comments, the Google Go style guide and these house rules:

Wrap errors with %w and add context; compare with errors.Is/errors.As.
context.Context is the first parameter and is never stored in a struct.
Suppress a finding only with //nolint:<linter> // reason.

Claude Code formats each .go file you edit and lints its package through a user-level hook, and reports findings back in the same session. Fix them before moving on.

Before opening a PR

Run all of these and make sure they pass (in a mise-activated shell, or prefix each with mise exec --):

go test ./...
go test -race ./...
go vet ./...
golangci-lint run ./...
./scripts/govulncheck.sh
go build ./cmd/wicket/

Reviews and worktrees

Reviews: with project-review, never team-pr-review, which .claude/settings.json denies here. Its facts and lenses for this project are in ~/code/gaius-codius-skills/projects/wicket/. Each review writes its record to ~/code/wicket/working-docs/reviews/.
Worktrees: make them under ~/code/wicket-worktrees/ with git worktree add from origin/main, then copy the untracked settings in and install the shared hooks, which live in the git-ignored lefthook-local.yml and so don't come with the worktree: mkdir -p <worktree>/.claude && cp ~/code/wicket/.claude/settings.json <worktree>/.claude/ && ~/code/robocode/tooling/install-local-hooks <worktree> go. Without them a commit stops at the shared hooks loaded check.

Install wicket 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": "gaius-codius-wicket-wicket", "kind": "skill", "name": "wicket", "description": "Read [CONTRIBUTING.md](CONTRIBUTING.md) for the toolchain, the checks to run before pushing, test rules, code style, and commit conventions. Those rules apply to agents too, including: no co-author, \"generated with\" or other tool attribution in commits or pull requests.", "publisher": "gaius-codius", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Read [CONTRIBUTING.md](CONTRIBUTING.md) for the toolchain, the checks to run before pushing, test rules, code style, and commit conventions. Those rules apply to agents too, including: no co-author, \"generated with\" or other tool attribution in commits or pull requests." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/gaius-codius/wicket", "path": "AGENTS.md", "ref": "87395312baca5b9226069b5435489aca145e9836", "url": "https://github.com/gaius-codius/wicket/blob/87395312baca5b9226069b5435489aca145e9836/AGENTS.md", "key": "gaius-codius/wicket/AGENTS.md" } }, "instructions": "# Agent instructions\n\nRead [CONTRIBUTING.md](CONTRIBUTING.md) for the toolchain, the checks to run\nbefore pushing, test rules, code style, and commit conventions. Those rules\napply to agents too, including: no co-author, \"generated with\" or other tool\nattribution in commits or pull requests.\n\n## What to work on\n\nWork is tracked in GitHub issues on the [project board](https://github.com/users/gaius-codius/projects/3).\n\n- **Epics** are parent issues labelled `type:epic`. Work items are native sub-issues of an epic.\n- **Types** are labels, exactly one per issue: `type:feature`, `type:research`, `", "cost": { "context_tokens": 820 } }

wicket

About

Agent instructions

What to work on

Go style

Before opening a PR

Reviews and worktrees

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