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.

kit-init - Prompt - OpenSmartRoute

Name: kit-init
Author: M-HamzaAdeem

Prompt file imported from M-HamzaAdeem/MarketDirectionPredictor (.claude/commands/kit-init.md). Copyright stays with the author.

Initialize this repository's project profile in one pass. The portable kit (CLAUDE.md, rules, agents) is stack-agnostic and defers every project specific to .claude/project/context.md; this command generates that file from the actual codebase so no manual editing is needed. Do all of the following, then report.

1. Inspect the repository

Detect the stack and layout from real evidence — do not guess. Probe for:

Stack & build: *.sln/*.csproj (.NET), package.json (Node — note the framework: React/Vue/Angular/Next), pyproject.toml/requirements.txt/setup.cfg (Python), go.mod (Go), Cargo.toml (Rust), pom.xml/build.gradle (JVM), Gemfile (Ruby).
Solution & folder layout: the top-level projects/packages and each one's responsibility (API/edge, application/services, domain, infrastructure, tests, UI).
Key libraries & canonical helpers: mapping, validation, logging, error handling, data access, testing — name the specific library used for each cross-cutting concern so Claude reuses it instead of inventing a new one.
Conventions: root namespace/module prefix, naming rules, anything that differs from the portable defaults in CLAUDE.md / the rules.
Build & run commands: restore/build, test, lint/format, and run-locally commands.

Read the placeholder at .claude/project/context.md for the exact section structure to fill. Use Glob/Grep/Read for inspection; you may run read-only Bash (e.g. git ls-files, dotnet --info) but make no source changes outside .claude/project/.

2. Trim to the detected stack (packs)

The kit ships every pack so a copy-paste install works anywhere; now trim to what this repo actually needs. Map the detected stack to packs:

*.sln/*.csproj (.NET) → keep dotnet
package.json with React/Vue, or *.tsx/*.vue files → keep frontend
neither → keep neither (core only)

Pack-specific files carry a pack: line in their frontmatter. Find the pack-tagged files under .claude/rules/ and .claude/agents/ (e.g. grep -rl "^pack:" .claude/rules .claude/agents), read each one's pack: value, and delete the files whose pack is not in the kept set (e.g. on a React repo, remove the pack: dotnet rules and agents). Then record the kept packs in .claude/.kit-packs — space-separated (e.g. frontend), or all if you kept everything. Tell the user which packs were kept and what was removed.

Skip this (leave the full kit in place) if you can't confidently determine the stack.

3. Generate the project profile

Rewrite .claude/project/context.md with the findings, following its existing headings. Remove the PLACEHOLDER — REPLACE THIS FILE banner comment at the top. Fill every section with concrete, verified facts; if something genuinely doesn't apply, say so briefly rather than leaving a bracketed placeholder.
Leave .claude/project/tech-debt.md and decisions.md as-is if they're still the empty register/log; they ship ready to use. (Do not invent debt or decision entries.)
Keep project-specific names OUT of the portable files — they belong only under .claude/project/. (The audit's leakage check enforces this.)

4. Wire the human-commit audit hook

If .githooks/pre-commit exists at the repo root, enable it so human commits are gated by the same audit Claude runs:

git config core.hooksPath .githooks

Tell the user this was set (and that it points git at .githooks/). Skip with a note if this isn't a git repo or .githooks/pre-commit is absent.

Then make sure line endings are protected: the hook and *.sh scripts must stay LF or they break on Linux/macOS. The installer ships a .gitattributes for this, but if the repo already had its own .gitattributes the installer skipped it — in that case, append these rules if they're missing:

*.sh        text eol=lf
.githooks/* text eol=lf
*.py        text eol=lf

5. Verify

Run the consistency audit and confirm it passes:

python .claude/scripts/claude-audit.py

If it reports FAIL, fix the cause (usually a broken link or a project name that leaked into a portable file) and re-run until it PASSES.

6. Report

Summarize: the detected stack & layout, which packs were kept and what was trimmed, what you wrote to context.md, whether the git hook was wired, and the final audit RESULT. Note anything you were unsure about so the user can refine context.md.

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

Initialize this repository's project profile in one pass. The portable kit (CLAUDE.md, rules, agents) is stack-agnostic and defers every project specific to `.claude/project/context.md`; this command generates that file from the actual codebase so no manual editing is needed. Do all of the following, then report. ## 1. Inspect the repository Detect the stack and layout from real evidence — do not guess. Probe for: - **Stack & build:** `*.sln`/`*.csproj` (.NET), `package.json` (Node — note the framework: React/Vue/Angular/Next), `pyproject.toml`/`requirements.txt`/`setup.cfg` (Python), `go.mod` (Go), `Cargo.toml` (Rust), `pom.xml`/`build.gradle` (JVM), `Gemfile` (Ruby). - **Solution & folder layout:** the top-level projects/packages and each one's responsibility (API/edge, application/services, domain, infrastructure, tests, UI). - **Key libraries & canonical helpers:** mapping, validation, logging, error handling, data access, testing — name the specific library used for each cross-cutting concern so Claude reuses it instead of inventing a new one. - **Conventions:** root namespace/module prefix, naming rules, anything that differs from the portable defaults in CLAUDE.md / the rules. - **Build & run commands:** restore/build, test, lint/format, and run-locally commands. Read the placeholder at `.claude/project/context.md` for the exact section structure to fill. Use `Glob`/`Grep`/`Read` for inspection; you may run read-only `Bash` (e.g. `git ls-files`, `dotnet --info`) but make no source changes outside `.claude/project/`. ## 2. Trim to the detected stack (packs) The kit ships **every pack** so a copy-paste install works anywhere; now trim to what this repo actually needs. Map the detected stack to packs: - `*.sln`/`*.csproj` (.NET) → keep **`dotnet`** - `package.json` with React/Vue, or `*.tsx`/`*.vue` files → keep **`frontend`** - neither → keep neither (core only) Pack-specific files carry a `pack:` line in their frontmatter. Find the pack-tagged files under `.claude/rules/` and `.claude/agents/` (e.g. `grep -rl "^pack:" .claude/rules .claude/agents`), read each one's `pack:` value, and **delete the files whose pack is not in the kept set** (e.g. on a React repo, remove the `pack: dotnet` rules and agents). Then record the kept packs in `.claude/.kit-packs` — space-separated (e.g. `frontend`), or `all` if you kept everything. Tell the user which packs were kept and what was removed. Skip this (leave the full kit in place) if you can't confidently determine the stack. ## 3. Generate the project profile - **Rewrite [`.claude/project/context.md`](../project/context.md)** with the findings, following its existing headings. **Remove the `PLACEHOLDER — REPLACE THIS FILE` banner comment** at the top. Fill every section with concrete, verified facts; if something genuinely doesn't apply, say so briefly rather than leaving a bracketed placeholder. - **Leave [`.claude/project/tech-debt.md`](../project/tech-debt.md) and [`decisions.md`](../project/decisions.md) as-is** if they're still the empty register/log; they ship ready to use. (Do not invent debt or decision entries.) - Keep project-specific names OUT of the portable files — they belong only under `.claude/project/`. (The audit's leakage check enforces this.) ## 4. Wire the human-commit audit hook If `.githooks/pre-commit` exists at the repo root, enable it so human commits are gated by the same audit Claude runs: ```sh git config core.hooksPath .githooks ``` Tell the user this was set (and that it points git at `.githooks/`). Skip with a note if this isn't a git repo or `.githooks/pre-commit` is absent. Then make sure line endings are protected: the hook and `*.sh` scripts must stay LF or they break on Linux/macOS. The installer ships a `.gitattributes` for this, but if the repo already had its own `.gitattributes` the installer skipped it — in that case, append these rules if they're missing: ``` *.sh text eol=lf .githooks/* text eol=lf *.py text eol=lf ``` ## 5. Verify Run the consistency audit and confirm it passes: ```sh python .claude/scripts/claude-audit.py ``` If it reports FAIL, fix the cause (usually a broken link or a project name that leaked into a portable file) and re-run until it PASSES. ## 6. Report Summarize: the detected stack & layout, **which packs were kept and what was trimmed**, what you wrote to `context.md`, whether the git hook was wired, and the final audit RESULT. Note anything you were unsure about so the user can refine `context.md`.

{ "prompt": "Initialize this repository's project profile in one pass. The portable kit (CLAUDE.md,\nrules, agents) is stack-agnostic and defers every project specific to\n`.claude/project/context.md`; this command generates that file from the actual codebase\nso no manual editing is needed. Do all of the following, then report.\n\n## 1. Inspect the repository\n\nDetect the stack and layout from real evidence — do not guess. Probe for:\n\n- **Stack & build:** `*.sln`/`*.csproj` (.NET), `package.json` (Node — note the framework:\n React/Vue/Angular/Next), `pyproject.toml`/`requirements.txt`/`setup.cfg` (Python),\n `go.mod` (Go), `Cargo.toml` (Rust), `pom.xml`/`build.gradle` (JVM), `Gemfile` (Ruby).\n- **Solution & folder layout:** the top-level projects/packages and each one's\n responsibility (API/edge, application/services, domain, infrastructure, tests, UI).\n- **Key libraries & canonical helpers:** mapping, validation, logging, error handling,\n data access, testing — name the specific library used for each cross-cutting concern so\n Claude reuses it instead of inventing a new one.\n- **Conventions:** root namespace/module prefix, naming rules, anything that differs from\n the portable defaults in CLAUDE.md / the rules.\n- **Build & run commands:** restore/build, test, lint/format, and run-locally commands.\n\nRead the placeholder at `.claude/project/context.md` for the exact section structure to\nfill. Use `Glob`/`Grep`/`Read` for inspection; you may run read-only `Bash` (e.g.\n`git ls-files`, `dotnet --info`) but make no source changes outside `.claude/project/`.\n\n## 2. Trim to the detected stack (packs)\n\nThe kit ships **every pack** so a copy-paste install works anywhere; now trim to what this\nrepo actually needs. Map the detected stack to packs:\n\n- `*.sln`/`*.csproj` (.NET) → keep **`dotnet`**\n- `package.json` with React/Vue, or `*.tsx`/`*.vue` files → keep **`frontend`**\n- neither → keep neither (core only)\n\nPack-specific files carry a `pack:` line in their frontmatter. Find the pack-tagged files\nunder `.claude/rules/` and `.claude/agents/` (e.g. `grep -rl \"^pack:\" .claude/rules .claude/agents`),\nread each one's `pack:` value, and **delete the files whose pack is not in the kept set**\n(e.g. on a React repo, remove the `pack: dotnet` rules and agents). Then record the kept\npacks in `.claude/.kit-packs` — space-separated (e.g. `frontend`), or `all` if you kept\neverything. Tell the user which packs were kept and what was removed.\n\nSkip this (leave the full kit in place) if you can't confidently determine the stack.\n\n## 3. Generate the project profile\n\n- **Rewrite [`.claude/project/context.md`](../project/context.md)** with the findings,\n following its existing headings. **Remove the `PLACEHOLDER — REPLACE THIS FILE` banner\n comment** at the top. Fill every section with concrete, verified facts; if something\n genuinely doesn't apply, say so briefly rather than leaving a bracketed placeholder.\n- **Leave [`.claude/project/tech-debt.md`](../project/tech-debt.md) and\n [`decisions.md`](../project/decisions.md) as-is** if they're still the empty register/log;\n they ship ready to use. (Do not invent debt or decision entries.)\n- Keep project-specific names OUT of the portable files — they belong only under\n `.claude/project/`. (The audit's leakage check enforces this.)\n\n## 4. Wire the human-commit audit hook\n\nIf `.githooks/pre-commit` exists at the repo root, enable it so human commits are gated\nby the same audit Claude runs:\n\n```sh\ngit config core.hooksPath .githooks\n```\n\nTell the user this was set (and that it points git at `.githooks/`). Skip with a note if\nthis isn't a git repo or `.githooks/pre-commit` is absent.\n\nThen make sure line endings are protected: the hook and `*.sh` scripts must stay LF or\nthey break on Linux/macOS. The installer ships a `.gitattributes` for this, but if the\nrepo already had its own `.gitattributes` the installer skipped it — in that case, append\nthese rules if they're missing:\n\n```\n*.sh text eol=lf\n.githooks/* text eol=lf\n*.py text eol=lf\n```\n\n## 5. Verify\n\nRun the consistency audit and confirm it passes:\n\n```sh\npython .claude/scripts/claude-audit.py\n```\n\nIf it reports FAIL, fix the cause (usually a broken link or a project name that leaked\ninto a portable file) and re-run until it PASSES.\n\n## 6. Report\n\nSummarize: the detected stack & layout, **which packs were kept and what was trimmed**,\nwhat you wrote to `context.md`, whether the git hook was wired, and the final audit RESULT.\nNote anything you were unsure about so the user can refine `context.md`.", "variables": [], "notes": "First-run setup for a freshly-installed kit — inspect this repo and generate .claude/project/context.md + tech-debt.md, wire the git audit hook, and verify. Tools: Read, Glob, Grep, Bash, Edit, Write.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/M-HamzaAdeem/MarketDirectionPredictor", "path": ".claude/commands/kit-init.md", "ref": "baa29232a5bbaf1bf78a7daaf37fe9b18315ca69", "url": "https://github.com/M-HamzaAdeem/MarketDirectionPredictor/blob/baa29232a5bbaf1bf78a7daaf37fe9b18315ca69/.claude/commands/kit-init.md", "key": "M-HamzaAdeem/MarketDirectionPredictor/.claude/commands/kit-init.md" } } }

kit-init

About

1. Inspect the repository

2. Trim to the detected stack (packs)

3. Generate the project profile

4. Wire the human-commit audit hook

5. Verify

6. Report

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