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.

explore - Prompt - OpenSmartRoute

Name: explore
Author: lgzarturo

Prompt file imported from lgzarturo/lgzarturo_cv (.cursor/commands/cc/explore.md). Fill in {{arguments}} before use. Copyright stays with the author.

Explore Workflow

Explore request: {{arguments}}

Step 0 — CCEP Bootstrap

Command: explore (fixed for this workflow — do not infer from user text)

Run: npx cc-codeconductor ccep profile explore --output json to get the phases and their roles.
For each delegated phase, run: npx cc-codeconductor ccep compile --command explore --phase <phase-id> "{{arguments}}" --view prompt --output json
After planner/intake JSON is available, run: npx cc-codeconductor ccep evaluate --command explore --input <planner.json> --output json. If stop is true, show questions or risks and wait for human input.
Pass each subagent only the compiled prompt for its phase — never forward raw {{arguments}} to planners.

Step 1 — Map (repo-explorer)

If graphify-out/graph.json exists, run graphify query "{{arguments}}". Invoke repo-explorer. Produce a Repo Map. Do not write code.

Step 2 — Suggest next command (orchestrator)

Recommend exactly one next slash command (/cc:feature, /cc:fix, /cc:refactor, /cc:review, /cc:backlog, /cc:openspec, /cc:triage, …) with a one-sentence rationale. Do not start that workflow.

Completion

Report the Repo Map and the recommended next /cc: command.

# Explore Workflow Explore request: {{arguments}} ## Step 0 — CCEP Bootstrap Command: `explore` (fixed for this workflow — do not infer from user text) 1. Run: `npx cc-codeconductor ccep profile explore --output json` to get the phases and their roles. 2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command explore --phase <phase-id> "{{arguments}}" --view prompt --output json` 3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command explore --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input. 4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `{{arguments}}` to planners. --- ## Step 1 — Map (repo-explorer) If `graphify-out/graph.json` exists, run `graphify query "{{arguments}}"`. Invoke `repo-explorer`. Produce a Repo Map. Do not write code. --- ## Step 2 — Suggest next command (orchestrator) Recommend exactly one next slash command (`/cc:feature`, `/cc:fix`, `/cc:refactor`, `/cc:review`, `/cc:backlog`, `/cc:openspec`, `/cc:triage`, …) with a one-sentence rationale. Do not start that workflow. --- ## Completion Report the Repo Map and the recommended next `/cc:` command.

Install explore 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": "# Explore Workflow\n\nExplore request: {{arguments}}\n\n## Step 0 — CCEP Bootstrap\n\nCommand: `explore` (fixed for this workflow — do not infer from user text)\n\n1. Run: `npx cc-codeconductor ccep profile explore --output json` to get the phases and their roles.\n2. For each delegated phase, run: `npx cc-codeconductor ccep compile --command explore --phase <phase-id> \"{{arguments}}\" --view prompt --output json`\n3. After planner/intake JSON is available, run: `npx cc-codeconductor ccep evaluate --command explore --input <planner.json> --output json`. If `stop` is true, show questions or risks and wait for human input.\n4. Pass each subagent only the compiled `prompt` for its phase — never forward raw `{{arguments}}` to planners.\n\n---\n\n## Step 1 — Map (repo-explorer)\n\nIf `graphify-out/graph.json` exists, run `graphify query \"{{arguments}}\"`. Invoke `repo-explorer`. Produce a Repo Map. Do not write code.\n\n---\n\n## Step 2 — Suggest next command (orchestrator)\n\nRecommend exactly one next slash command (`/cc:feature`, `/cc:fix`, `/cc:refactor`, `/cc:review`, `/cc:backlog`, `/cc:openspec`, `/cc:triage`, …) with a one-sentence rationale. Do not start that workflow.\n\n---\n\n## Completion\n\nReport the Repo Map and the recommended next `/cc:` command.", "variables": [ "arguments" ], "notes": "Map the repository and recommend the next CodeConductor slash command. Read-only.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/lgzarturo/lgzarturo_cv", "path": ".cursor/commands/cc/explore.md", "ref": "aff9a896e42d9f3dbba0c526ccf66dcaaf2abd75", "url": "https://github.com/lgzarturo/lgzarturo_cv/blob/aff9a896e42d9f3dbba0c526ccf66dcaaf2abd75/.cursor/commands/cc/explore.md", "key": "lgzarturo/lgzarturo_cv/.cursor/commands/cc/explore.md" } } }

explore

About

Explore Workflow

Step 0 — CCEP Bootstrap

Step 1 — Map (repo-explorer)

Step 2 — Suggest next command (orchestrator)

Completion

Use it

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

Manifest

Reviews