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.

hako.ranma - Skill - OpenSmartRoute

Name: hako.ranma
Author: masshirodev

Imported from masshirodev/hako.ranma (AGENTS.md). Install upstream with npx skills add masshirodev/hako.ranma. Copyright stays with the author.

AGENTS.md

hako is a plugin manager for ranma (~/projects/ranma, masshirodev/ranma), written as a ranma plugin in Lua. README.md is the user's reference; doc/DESIGN.md records the decisions, including what it deliberately does not do (lazy-loading). Read both before changing behaviour.

Layout

lua/hako/init.lua: setup(), reading specs and loading plugins with ranma.packadd.
lua/hako/spec.lua: parsing specs, strictly; lua/hako/ops.lua: the background operations; lua/hako/task.lua: coroutines over ranma.spawn; lua/hako/screen.lua: the screen (doc/SCREEN.md); lua/hako/ui.lua: the palette command, the key and the bar module; lua/hako/lock.lua, lua/hako/util.lua, lua/hako/state.lua.
There is no plugin/ directory: hako runs when init.lua calls setup.

Before a commit

tests/e2e.sh

It starts a private, headless ranma (its own runtime, state and config directories, its own tmux server) and never touches a real session. ranma lua and ranma action talk to whatever RANMA_SOCKET names, and every ranma pane exports it: a test that does not set it to its own server's socket drives the user's real ranma. Keep the env -u RANMA_SOCKET … and the explicit RANMA_SOCKET=$RT/ranma/1.sock in place.

A change to behaviour comes with a step in tests/e2e.sh, a line in README.md, and, for a decision, doc/DESIGN.md.

Conventions

Push to main.
ranma's API is the reference: ranma --dump-types prints it. Only binds, options, hooks and packadd work while loading; spawn, toast, action and pickers only at run time (util.later defers to the first tick).
Nothing hako does may fail init.lua: errors are caught, kept on the plugin and toasted.
Specs are parsed strictly, as ranma parses its config: an unknown field is an error naming it, never ignored.
Never delete anything without asking, and never anything a spec still declares or that hako did not clone (dir checkouts, pack/*/start).

Install hako.ranma 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": "masshirodev-hako-ranma-hako-ranma", "kind": "skill", "name": "hako.ranma", "description": "hako is a plugin manager for ranma (`~/projects/ranma`, `masshirodev/ranma`), written as a ranma plugin in Lua. `README.md` is the user's reference; `doc/DESIGN.md` records the decisions, including what it deliberately does not do (lazy-loading). Read both before changing behaviour.", "publisher": "masshirodev", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "hako is a plugin manager for ranma (`~/projects/ranma`, `masshirodev/ranma`), written as a ranma plugin in Lua. `README.md` is the user's reference; `doc/DESIGN.md` records the decisions, including what it deliberately does not do (lazy-loading). Read both before changing behaviour." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/masshirodev/hako.ranma", "path": "AGENTS.md", "ref": "2b79e3253bfc468264a172cdec25cd4b70a1570c", "url": "https://github.com/masshirodev/hako.ranma/blob/2b79e3253bfc468264a172cdec25cd4b70a1570c/AGENTS.md", "key": "masshirodev/hako.ranma/AGENTS.md" } }, "instructions": "# AGENTS.md\n\nhako is a plugin manager for ranma (`~/projects/ranma`, `masshirodev/ranma`),\nwritten as a ranma plugin in Lua. `README.md` is the user's reference;\n`doc/DESIGN.md` records the decisions, including what it deliberately does not\ndo (lazy-loading). Read both before changing behaviour.\n\n## Layout\n\n- `lua/hako/init.lua`: `setup()`, reading specs and loading plugins with\n `ranma.packadd`.\n- `lua/hako/spec.lua`: parsing specs, strictly; `lua/hako/ops.lua`: the\n background operations; `lua/hako/task.lua`: coroutines over `ranma.spawn`;\n `lua/hako/screen.lua`: the screen (`doc/SCREEN.m", "cost": { "context_tokens": 504 } }

hako.ranma

About

AGENTS.md

Layout

Before a commit

Conventions

Install hako.ranma 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