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.

cleanup - Prompt - OpenSmartRoute

Prompt file imported from TsuyoshiUshio/buka-samples (.github/prompts/cleanup.prompt.md). Copyright stays with the author.

Cleanup — Checklist Files

Respond in the language the user is using in the chat.

Remove or archive completed checklist files from the project root.

Procedure

List all checklist files in the project root matching checklist-*.md.
For each file, read it and check its status:
- If ALL steps are marked [x] (complete) or [~] (skipped): it is done.
- If any steps are still [ ] (incomplete): it is in progress.

Show a summary to the user:

Checklist files found:
✅ checklist-setup-gmail-api.md — all steps complete
✅ checklist-add-calendar-feature.md — all steps complete
🔄 checklist-write-parser.md — 3 of 5 steps complete

Ask the user what to do with the completed files:
- Delete: Remove completed checklist files permanently.
- Keep: Leave everything as-is.
Execute the user's choice. Never delete in-progress checklists.

# Cleanup — Checklist Files > Respond in the language the user is using in the chat. Remove or archive completed checklist files from the project root. ## Procedure 1. **List all checklist files** in the project root matching `checklist-*.md`. 2. **For each file**, read it and check its status: - If ALL steps are marked `[x]` (complete) or `[~]` (skipped): it is **done**. - If any steps are still `[ ]` (incomplete): it is **in progress**. 3. **Show a summary** to the user: ```text Checklist files found: ✅ checklist-setup-gmail-api.md — all steps complete ✅ checklist-add-calendar-feature.md — all steps complete 🔄 checklist-write-parser.md — 3 of 5 steps complete ``` 4. **Ask the user** what to do with the completed files: - **Delete**: Remove completed checklist files permanently. - **Keep**: Leave everything as-is. 5. **Execute** the user's choice. Never delete in-progress checklists.

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

cleanup

About

Cleanup — Checklist Files

Procedure

Use it

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