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.

init - Prompt - OpenSmartRoute

Name: init
Author: nguyenntdev

Prompt file imported from nguyenntdev/luuniensuki-lms (.cursor/commands/init.md). Copyright stays with the author.

What to add:

Commands that will be commonly used, such as how to build, lint, and run tests. Include the necessary commands to develop in this codebase, such as how to run a single test.
High-level code architecture and structure so that future instances can be productive more quickly. Focus on the "big picture" architecture that requires reading multiple files to understand
Special logic and unique patterns in the codebase - retrieve and document any non-standard implementations, custom conventions, edge case handling, workarounds, or domain-specific logic that deviates from common patterns. Do not skip or overlook these special cases.

Usage notes:

If there's already a CLAUDE.md, suggest improvements to it.
When you make the initial CLAUDE.md, do not repeat yourself and do not include obvious instructions like "Provide helpful error messages to users", "Write unit tests for all new utilities", "Never include sensitive information (API keys, tokens) in code or commits"
Avoid listing every component or file structure that can be easily discovered
Don't include generic development practices
If there are Cursor rules (in .cursor/commands/ or .cursorrules) or Copilot rules (in .github/copilot-instructions.md), make sure to include the important parts.
If there is a README.md, make sure to include the important parts.
Do not make up information such as "Common Development Tasks", "Tips for Development", "Support and Documentation" unless this is expressly included in other files that you read.
Pay special attention to documenting unique logic, special cases, and non-obvious implementation details that future instances need to be aware of to avoid breaking existing functionality.
Be sure to prefix the file with the following text:

# CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Install init 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.

Please analyze this codebase and create a CLAUDE.md file, which will be given to future instances of Claude Code to operate in this repository. Use the codebase-retrieval tool to retrieve and analyze the codebase. What to add: 1. Commands that will be commonly used, such as how to build, lint, and run tests. Include the necessary commands to develop in this codebase, such as how to run a single test. 2. High-level code architecture and structure so that future instances can be productive more quickly. Focus on the "big picture" architecture that requires reading multiple files to understand 3. Special logic and unique patterns in the codebase - retrieve and document any non-standard implementations, custom conventions, edge case handling, workarounds, or domain-specific logic that deviates from common patterns. Do not skip or overlook these special cases. Usage notes: - If there's already a CLAUDE.md, suggest improvements to it. - When you make the initial CLAUDE.md, do not repeat yourself and do not include obvious instructions like "Provide helpful error messages to users", "Write unit tests for all new utilities", "Never include sensitive information (API keys, tokens) in code or commits" - Avoid listing every component or file structure that can be easily discovered - Don't include generic development practices - If there are Cursor rules (in .cursor/commands/ or .cursorrules) or Copilot rules (in .github/copilot-instructions.md), make sure to include the important parts. - If there is a README.md, make sure to include the important parts. - Do not make up information such as "Common Development Tasks", "Tips for Development", "Support and Documentation" unless this is expressly included in other files that you read. - Pay special attention to documenting unique logic, special cases, and non-obvious implementation details that future instances need to be aware of to avoid breaking existing functionality. - Be sure to prefix the file with the following text: ``` # CLAUDE.md This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. ```

{ "prompt": "Please analyze this codebase and create a CLAUDE.md file, which will be given to future instances of Claude Code to operate in this repository. Use the codebase-retrieval tool to retrieve and analyze the codebase.\n\nWhat to add:\n\n1. Commands that will be commonly used, such as how to build, lint, and run tests. Include the necessary commands to develop in this codebase, such as how to run a single test.\n2. High-level code architecture and structure so that future instances can be productive more quickly. Focus on the \"big picture\" architecture that requires reading multiple files to understand\n3. Special logic and unique patterns in the codebase - retrieve and document any non-standard implementations, custom conventions, edge case handling, workarounds, or domain-specific logic that deviates from common patterns. Do not skip or overlook these special cases.\n\nUsage notes:\n\n- If there's already a CLAUDE.md, suggest improvements to it.\n- When you make the initial CLAUDE.md, do not repeat yourself and do not include obvious instructions like \"Provide helpful error messages to users\", \"Write unit tests for all new utilities\", \"Never include sensitive information (API keys, tokens) in code or commits\"\n- Avoid listing every component or file structure that can be easily discovered\n- Don't include generic development practices\n- If there are Cursor rules (in .cursor/commands/ or .cursorrules) or Copilot rules (in .github/copilot-instructions.md), make sure to include the important parts.\n- If there is a README.md, make sure to include the important parts.\n- Do not make up information such as \"Common Development Tasks\", \"Tips for Development\", \"Support and Documentation\" unless this is expressly included in other files that you read.\n- Pay special attention to documenting unique logic, special cases, and non-obvious implementation details that future instances need to be aware of to avoid breaking existing functionality.\n- Be sure to prefix the file with the following text:\n\n```\n# CLAUDE.md\n\nThis file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.\n```", "variables": [], "notes": "/init", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/nguyenntdev/luuniensuki-lms", "path": ".cursor/commands/init.md", "ref": "e19aebc0e7f66f7863659fd658c204739e199687", "url": "https://github.com/nguyenntdev/luuniensuki-lms/blob/e19aebc0e7f66f7863659fd658c204739e199687/.cursor/commands/init.md", "key": "nguyenntdev/luuniensuki-lms/.cursor/commands/init.md" } } }

init

About

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