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.

new-plugin - Prompt - OpenSmartRoute

Name: new-plugin
Author: academic-moodle-cooperation

Prompt file imported from academic-moodle-cooperation/management-ui (.claude/commands/new-plugin.md). Fill in {{arguments}} before use. Copyright stays with the author.

Scaffold a new plugin ({{arguments}}) and finish wiring it per AGENTS.md.

Pick the location (confirm with me if it's ambiguous):
- pnpm create-plugin <name> → .local-plugins/<name>/ (gitignored; for org / community plugins; ships a Maven backend/ POM by default — pass --no-pom to skip).
- pnpm create-plugin <name> --in-tree → plugins/<name>/ (a built-in plugin shipped with the OSS repo; no Maven layout). Only for core contributors.
- Add --template app for a visible screen + sidebar entry; the default minimal template is a placeholder app:header-logo registration with no visible effect.
Run the scaffolder. It writes the canonical layout (package.json, plugin.json, tsconfig.json, vitest.config.ts, src/index.ts, src/plugin.contract.test.ts) and runs pnpm install to link the package into the workspace.
Confirm the contract test is green out of the box: pnpm --filter @oc-mui/plugin-<name> test:contract.
Replace the placeholder. Update src/index.ts's initialize() registrations and keep plugin.json's extensionPoints array in sync — the contract test fails if a declared extension point isn't populated (or vice-versa). Keep all manager.registerObject(...) calls in initialize(), not activate().
Respect the boundaries (AGENTS.md → Boundaries). The plugin may import only @oc-mui/*, plugins/core, itself, and already-wrapped third-party libs. Never import from apps/*, another plugin, or a wrapped library directly (use @oc-mui/router, not @tanstack/react-router; @oc-mui/query, @oc-mui/i18n, @oc-mui/store likewise).

A .local-plugins/ plugin is never added to plugins/index.ts. When the plugin work is done, run the pre-flight-check skill (or /verify) before declaring it complete.

Install new-plugin 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.

{ "prompt": "Scaffold a new plugin (`{{arguments}}`) and finish wiring it per `AGENTS.md`.\n\n1. **Pick the location** (confirm with me if it's ambiguous):\n - `pnpm create-plugin <name>` → `.local-plugins/<name>/` (gitignored; for org /\n community plugins; ships a Maven `backend/` POM by default — pass `--no-pom` to skip).\n - `pnpm create-plugin <name> --in-tree` → `plugins/<name>/` (a built-in plugin shipped\n with the OSS repo; no Maven layout). Only for core contributors.\n - Add `--template app` for a visible screen + sidebar entry; the default `minimal`\n template is a placeholder `app:header-logo` registration with no visible effect.\n\n2. **Run the scaffolder.** It writes the canonical layout (`package.json`, `plugin.json`,\n `tsconfig.json`, `vitest.config.ts`, `src/index.ts`, `src/plugin.contract.test.ts`)\n and runs `pnpm install` to link the package into the workspace.\n\n3. **Confirm the contract test is green out of the box:**\n `pnpm --filter @oc-mui/plugin-<name> test:contract`.\n\n4. **Replace the placeholder.** Update `src/index.ts`'s `initialize()` registrations and\n keep `plugin.json`'s `extensionPoints` array in sync — the contract test fails if a\n declared extension point isn't populated (or vice-versa). Keep all\n `manager.registerObject(...)` calls in `initialize()`, not `activate()`.\n\n5. **Respect the boundaries** (AGENTS.md → Boundaries). The plugin may import only\n `@oc-mui/*`, `plugins/core`, itself, and already-wrapped third-party libs. Never\n import from `apps/*`, another plugin, or a wrapped library directly (use\n `@oc-mui/router`, not `@tanstack/react-router`; `@oc-mui/query`, `@oc-mui/i18n`,\n `@oc-mui/store` likewise).\n\nA `.local-plugins/` plugin is **never** added to `plugins/index.ts`. When the plugin\nwork is done, run the `pre-flight-check` skill (or `/verify`) before declaring it complete.", "variables": [ "arguments" ], "notes": "Scaffold a new plugin and wire it to the AGENTS.md layout Tools: Bash(pnpm create-plugin:*), Bash(pnpm install:*), Bash(pnpm test:*), Read, Edit, Glob, Grep. Arguments: <plugin-name> [--in-tree] [--template app].", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/academic-moodle-cooperation/management-ui", "path": ".claude/commands/new-plugin.md", "ref": "86fa647e0ebf35c5c09b8cc9f7ba7ec17107640f", "url": "https://github.com/academic-moodle-cooperation/management-ui/blob/86fa647e0ebf35c5c09b8cc9f7ba7ec17107640f/.claude/commands/new-plugin.md", "key": "academic-moodle-cooperation/management-ui/.claude/commands/new-plugin.md" } } }

new-plugin

About

Install new-plugin 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