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.

rapidx:plugin - Prompt - OpenSmartRoute

Name: rapidx:plugin
Author: dbrijesh

Prompt file imported from dbrijesh/mgpdemo (.claude/commands/rapidx/plugin.md). Fill in {{arguments}} before use. Copyright stays with the author.

Usage: /rapidx:plugin list → Show all available plugins /rapidx:plugin install → Install a plugin /rapidx:plugin install --all-platforms → Install for all configured platforms /rapidx:plugin remove → Remove a plugin /rapidx:plugin info → Show plugin details

Mode: list (no arguments or "list")

Display all available plugins:

RapidX Plugin Catalog

  SDLC Workflow Plugins:
    sdd-workflow@1.0.0         Spec-Driven Development full workflow bundle
    knowledge-engine@1.0.0     Codebase learning and fine-tuning system
    full-sdlc@1.0.0            Complete SDLC: SDD + knowledge + governance

  Governance Plugins:
    enterprise-governance@1.0.0  Enterprise governance, compliance, audit trail

  Stack-Specific Plugins:
    frontend-react@1.0.0       React + TypeScript development bundle
    python-fastapi@1.0.0       Python + FastAPI backend bundle

  CI/CD Plugins:
    github-actions-sdlc@1.0.0  AI-powered GitHub Actions workflows

  [installed] = currently installed in this project

  Install: /rapidx:plugin install <name>

Mode: install

Locate plugin definition (built-in catalog or .rapidx/plugins/registry.json)
Check stack compatibility (if plugin has stackRequires)

Show installation plan:

Installing plugin: {name}@{version}

  Adds skills: {list}
  Adds agents: {list}
  Adds commands: {list}
  Adds hooks: {list}
  Adds workflows: {list}

  Proceed? [Y/n]

Copy components to installed locations
Update .rapidx/plugins/installed.json
Run /rapidx:knowledge-sync to propagate to all platforms
Output:

Plugin installed: {name}@{version}

  Components added:
    Skills:    {list}
    Agents:    {list}
    Commands:  {list}
    Hooks:     {list}

  Run /rapidx:help to see updated command list.

Mode: remove

Read .rapidx/plugins/installed.json
Confirm removal (destructive operation)
Remove plugin record from installed.json
Output cleanup instructions (components to manually remove if needed)

Mode: info

Display full plugin details:

Description
Version
Components included (skills, agents, commands, hooks)
Platform support
Stack requirements
Installation status

Creating custom plugins

To create a custom plugin for your team:

Create rapidx-plugin.json manifest:

{
  "name": "my-team-standards",
  "version": "1.0.0",
  "description": "My team's coding standards and agents",
  "author": "My Team",
  "platforms": ["claude", "vscode", "cursor"],
  "components": {
    "skills": ["my-skill"],
    "agents": ["my-agent"],
    "commands": ["my-command"],
    "hooks": []
  }
}

Add components in agents/, skills/, commands/ subdirectories
Register: add to .rapidx/plugins/registry.json
Install: /rapidx:plugin install my-team-standards

Install rapidx: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.

<objective> Manage RapidX plugins — curated bundles of agents + skills + instructions + hooks for specific workflows, frameworks, or compliance domains. Usage: /rapidx:plugin list → Show all available plugins /rapidx:plugin install <name> → Install a plugin /rapidx:plugin install <name> --all-platforms → Install for all configured platforms /rapidx:plugin remove <name> → Remove a plugin /rapidx:plugin info <name> → Show plugin details </objective> <process> ## Detect mode from {{arguments}} ### Mode: list (no arguments or "list") Display all available plugins: ``` RapidX Plugin Catalog SDLC Workflow Plugins: sdd-workflow@1.0.0 Spec-Driven Development full workflow bundle knowledge-engine@1.0.0 Codebase learning and fine-tuning system full-sdlc@1.0.0 Complete SDLC: SDD + knowledge + governance Governance Plugins: enterprise-governance@1.0.0 Enterprise governance, compliance, audit trail Stack-Specific Plugins: frontend-react@1.0.0 React + TypeScript development bundle python-fastapi@1.0.0 Python + FastAPI backend bundle CI/CD Plugins: github-actions-sdlc@1.0.0 AI-powered GitHub Actions workflows [installed] = currently installed in this project Install: /rapidx:plugin install <name> ``` ### Mode: install <name> 1. Locate plugin definition (built-in catalog or `.rapidx/plugins/registry.json`) 2. Check stack compatibility (if plugin has `stackRequires`) 3. Show installation plan: ``` Installing plugin: {name}@{version} Adds skills: {list} Adds agents: {list} Adds commands: {list} Adds hooks: {list} Adds workflows: {list} Proceed? [Y/n] ``` 4. Copy components to installed locations 5. Update `.rapidx/plugins/installed.json` 6. Run `/rapidx:knowledge-sync` to propagate to all platforms 7. Output: ``` Plugin installed: {name}@{version} Components added: Skills: {list} Agents: {list} Commands: {list} Hooks: {list} Run /rapidx:help to see updated command list. ``` ### Mode: remove <name> 1. Read `.rapidx/plugins/installed.json` 2. Confirm removal (destructive operation) 3. Remove plugin record from installed.json 4. Output cleanup instructions (components to manually remove if needed) ### Mode: info <name> Display full plugin details: - Description - Version - Components included (skills, agents, commands, hooks) - Platform support - Stack requirements - Installation status ### Creating custom plugins To create a custom plugin for your team: 1. Create `rapidx-plugin.json` manifest: ```json { "name": "my-team-standards", "version": "1.0.0", "description": "My team's coding standards and agents", "author": "My Team", "platforms": ["claude", "vscode", "cursor"], "components": { "skills": ["my-skill"], "agents": ["my-agent"], "commands": ["my-command"], "hooks": [] } } ``` 2. Add components in `agents/`, `skills/`, `commands/` subdirectories 3. Register: add to `.rapidx/plugins/registry.json` 4. Install: `/rapidx:plugin install my-team-standards` </process>

{ "prompt": "<objective>\nManage RapidX plugins — curated bundles of agents + skills + instructions + hooks for specific workflows, frameworks, or compliance domains.\n\nUsage:\n /rapidx:plugin list → Show all available plugins\n /rapidx:plugin install <name> → Install a plugin\n /rapidx:plugin install <name> --all-platforms → Install for all configured platforms\n /rapidx:plugin remove <name> → Remove a plugin\n /rapidx:plugin info <name> → Show plugin details\n</objective>\n\n<process>\n## Detect mode from {{arguments}}\n\n### Mode: list (no arguments or \"list\")\n\nDisplay all available plugins:\n\n```\nRapidX Plugin Catalog\n\n SDLC Workflow Plugins:\n sdd-workflow@1.0.0 Spec-Driven Development full workflow bundle\n knowledge-engine@1.0.0 Codebase learning and fine-tuning system\n full-sdlc@1.0.0 Complete SDLC: SDD + knowledge + governance\n\n Governance Plugins:\n enterprise-governance@1.0.0 Enterprise governance, compliance, audit trail\n\n Stack-Specific Plugins:\n frontend-react@1.0.0 React + TypeScript development bundle\n python-fastapi@1.0.0 Python + FastAPI backend bundle\n\n CI/CD Plugins:\n github-actions-sdlc@1.0.0 AI-powered GitHub Actions workflows\n\n [installed] = currently installed in this project\n\n Install: /rapidx:plugin install <name>\n```\n\n### Mode: install <name>\n\n1. Locate plugin definition (built-in catalog or `.rapidx/plugins/registry.json`)\n2. Check stack compatibility (if plugin has `stackRequires`)\n3. Show installation plan:\n ```\n Installing plugin: {name}@{version}\n\n Adds skills: {list}\n Adds agents: {list}\n Adds commands: {list}\n Adds hooks: {list}\n Adds workflows: {list}\n\n Proceed? [Y/n]\n ```\n4. Copy components to installed locations\n5. Update `.rapidx/plugins/installed.json`\n6. Run `/rapidx:knowledge-sync` to propagate to all platforms\n7. Output:\n\n```\nPlugin installed: {name}@{version}\n\n Components added:\n Skills: {list}\n Agents: {list}\n Commands: {list}\n Hooks: {list}\n\n Run /rapidx:help to see updated command list.\n```\n\n### Mode: remove <name>\n\n1. Read `.rapidx/plugins/installed.json`\n2. Confirm removal (destructive operation)\n3. Remove plugin record from installed.json\n4. Output cleanup instructions (components to manually remove if needed)\n\n### Mode: info <name>\n\nDisplay full plugin details:\n- Description\n- Version\n- Components included (skills, agents, commands, hooks)\n- Platform support\n- Stack requirements\n- Installation status\n\n### Creating custom plugins\n\nTo create a custom plugin for your team:\n\n1. Create `rapidx-plugin.json` manifest:\n```json\n{\n \"name\": \"my-team-standards\",\n \"version\": \"1.0.0\",\n \"description\": \"My team's coding standards and agents\",\n \"author\": \"My Team\",\n \"platforms\": [\"claude\", \"vscode\", \"cursor\"],\n \"components\": {\n \"skills\": [\"my-skill\"],\n \"agents\": [\"my-agent\"],\n \"commands\": [\"my-command\"],\n \"hooks\": []\n }\n}\n```\n\n2. Add components in `agents/`, `skills/`, `commands/` subdirectories\n3. Register: add to `.rapidx/plugins/registry.json`\n4. Install: `/rapidx:plugin install my-team-standards`\n</process>", "variables": [ "arguments" ], "notes": "Install, list, and manage RapidX plugins — curated bundles of agents, skills, and workflows Tools: Read, Write, Bash.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/dbrijesh/mgpdemo", "path": ".claude/commands/rapidx/plugin.md", "ref": "cf4326d25b4f98253b9cddbad775a93e0ebf2abe", "url": "https://github.com/dbrijesh/mgpdemo/blob/cf4326d25b4f98253b9cddbad775a93e0ebf2abe/.claude/commands/rapidx/plugin.md", "key": "dbrijesh/mgpdemo/.claude/commands/rapidx/plugin.md" } } }

rapidx:plugin

About

Mode: list (no arguments or "list")

Mode: install

Mode: remove

Mode: info

Creating custom plugins

Install rapidx: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