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.

security-alerts - Prompt - OpenSmartRoute

Name: security-alerts
Author: brianespinosa

Prompt file imported from brianespinosa/dotfiles (.claude/commands/gh/security-alerts.md). Copyright stays with the author.

Fetch and display GitHub Dependabot security alerts for the current workspace.

Step 1 — Detect context

pwd

Find the innermost (last/deepest) @-prefixed segment in the path, then check whether there is a non-@ segment immediately after it:

An @<name>_emu directory (innermost, no non-@ segment after) → EMU context
@brianespinosa (innermost, no non-@ segment after) → User context (login: brianespinosa)
@brianespinosa/<repo> (non-@ segment present after innermost) → Single-repo context (owner/repo = brianespinosa/<repo>)
Any other @<name> (innermost, no non-@ segment after) → Org context (org: <name> without the @)
Any other @<name>/<repo> (non-@ segment present after innermost) → Single-repo context (owner/repo = <name>/<repo>)

The innermost @-prefixed segment is the last path component starting with @. The repo segment is the path component immediately after it that does NOT start with @ — ignore anything deeper.

Step 2 — Run

Single-repo context (OWNER/REPO = derived above):

$HOME/.claude/commands/gh/gh-security-alerts.sh repo $OWNER/$REPO \
  | $HOME/.claude/commands/gh/gh-security-format.sh

User context:

$HOME/.claude/commands/gh/gh-security-alerts.sh user brianespinosa \
  | $HOME/.claude/commands/gh/gh-security-format.sh

Org context (ORG = segment name without @):

$HOME/.claude/commands/gh/gh-security-alerts.sh org $ORG \
  | $HOME/.claude/commands/gh/gh-security-format.sh

EMU context: Fetch only the orgs the authenticated user has admin access to, then run in parallel:

WORK=$(mktemp -d)
trap "rm -rf $WORK" EXIT
while IFS= read -r ORG; do
  ($HOME/.claude/commands/gh/gh-security-alerts.sh org-alerts "$ORG" > "$WORK/$ORG.ndjson") &
done < <(gh api '/user/memberships/orgs?state=active&per_page=100' --paginate \
  --jq '.[] | select(.role == "admin") | .organization.login')
wait
cat "$WORK"/*.ndjson | $HOME/.claude/commands/gh/gh-security-format-emu.sh

Step 3 — Display

Print the script output verbatim as markdown. Do not reformat, summarize, or add commentary.

Install security-alerts 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.

Fetch and display GitHub Dependabot security alerts for the current workspace. ## Step 1 — Detect context ```bash pwd ``` Find the **innermost (last/deepest) `@`-prefixed segment** in the path, then check whether there is a non-`@` segment immediately after it: - An `@<name>_emu` directory (innermost, no non-`@` segment after) → **EMU context** - `@brianespinosa` (innermost, no non-`@` segment after) → **User context** (login: `brianespinosa`) - `@brianespinosa/<repo>` (non-`@` segment present after innermost) → **Single-repo context** (`owner/repo` = `brianespinosa/<repo>`) - Any other `@<name>` (innermost, no non-`@` segment after) → **Org context** (org: `<name>` without the `@`) - Any other `@<name>/<repo>` (non-`@` segment present after innermost) → **Single-repo context** (`owner/repo` = `<name>/<repo>`) The innermost `@`-prefixed segment is the last path component starting with `@`. The repo segment is the path component immediately after it that does NOT start with `@` — ignore anything deeper. ## Step 2 — Run **Single-repo context** (`OWNER/REPO` = derived above): ```bash $HOME/.claude/commands/gh/gh-security-alerts.sh repo $OWNER/$REPO \ | $HOME/.claude/commands/gh/gh-security-format.sh ``` **User context:** ```bash $HOME/.claude/commands/gh/gh-security-alerts.sh user brianespinosa \ | $HOME/.claude/commands/gh/gh-security-format.sh ``` **Org context** (`ORG` = segment name without `@`): ```bash $HOME/.claude/commands/gh/gh-security-alerts.sh org $ORG \ | $HOME/.claude/commands/gh/gh-security-format.sh ``` **EMU context:** Fetch only the orgs the authenticated user has admin access to, then run in parallel: ```bash WORK=$(mktemp -d) trap "rm -rf $WORK" EXIT while IFS= read -r ORG; do ($HOME/.claude/commands/gh/gh-security-alerts.sh org-alerts "$ORG" > "$WORK/$ORG.ndjson") & done < <(gh api '/user/memberships/orgs?state=active&per_page=100' --paginate \ --jq '.[] | select(.role == "admin") | .organization.login') wait cat "$WORK"/*.ndjson | $HOME/.claude/commands/gh/gh-security-format-emu.sh ``` ## Step 3 — Display Print the script output verbatim as markdown. Do not reformat, summarize, or add commentary.

{ "prompt": "Fetch and display GitHub Dependabot security alerts for the current workspace.\n\n## Step 1 — Detect context\n\n```bash\npwd\n```\n\nFind the **innermost (last/deepest) `@`-prefixed segment** in the path, then check whether there is a non-`@` segment immediately after it:\n\n- An `@<name>_emu` directory (innermost, no non-`@` segment after) → **EMU context**\n- `@brianespinosa` (innermost, no non-`@` segment after) → **User context** (login: `brianespinosa`)\n- `@brianespinosa/<repo>` (non-`@` segment present after innermost) → **Single-repo context** (`owner/repo` = `brianespinosa/<repo>`)\n- Any other `@<name>` (innermost, no non-`@` segment after) → **Org context** (org: `<name>` without the `@`)\n- Any other `@<name>/<repo>` (non-`@` segment present after innermost) → **Single-repo context** (`owner/repo` = `<name>/<repo>`)\n\nThe innermost `@`-prefixed segment is the last path component starting with `@`. The repo segment is the path component immediately after it that does NOT start with `@` — ignore anything deeper.\n\n## Step 2 — Run\n\n**Single-repo context** (`OWNER/REPO` = derived above):\n```bash\n$HOME/.claude/commands/gh/gh-security-alerts.sh repo $OWNER/$REPO \\\n | $HOME/.claude/commands/gh/gh-security-format.sh\n```\n\n**User context:**\n```bash\n$HOME/.claude/commands/gh/gh-security-alerts.sh user brianespinosa \\\n | $HOME/.claude/commands/gh/gh-security-format.sh\n```\n\n**Org context** (`ORG` = segment name without `@`):\n```bash\n$HOME/.claude/commands/gh/gh-security-alerts.sh org $ORG \\\n | $HOME/.claude/commands/gh/gh-security-format.sh\n```\n\n**EMU context:** Fetch only the orgs the authenticated user has admin access to, then run in parallel:\n```bash\nWORK=$(mktemp -d)\ntrap \"rm -rf $WORK\" EXIT\nwhile IFS= read -r ORG; do\n ($HOME/.claude/commands/gh/gh-security-alerts.sh org-alerts \"$ORG\" > \"$WORK/$ORG.ndjson\") &\ndone < <(gh api '/user/memberships/orgs?state=active&per_page=100' --paginate \\\n --jq '.[] | select(.role == \"admin\") | .organization.login')\nwait\ncat \"$WORK\"/*.ndjson | $HOME/.claude/commands/gh/gh-security-format-emu.sh\n```\n\n## Step 3 — Display\n\nPrint the script output verbatim as markdown. Do not reformat, summarize, or add commentary.", "variables": [], "notes": "Show a Dependabot security alert report for the current context. Scope is determined automatically from the working directory: running inside a repo directory reports alerts for that repo only; running in a user or org directory reports alerts across all repos for that user or org; running in an EMU directory reports a per-repo count summary for each child org. Tools: Bash(pwd), Bash(*/.claude/commands/gh/gh-security-*).", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/brianespinosa/dotfiles", "path": ".claude/commands/gh/security-alerts.md", "ref": "c208bb3c1c6ed88144b911024fcfb309fc13af45", "url": "https://github.com/brianespinosa/dotfiles/blob/c208bb3c1c6ed88144b911024fcfb309fc13af45/.claude/commands/gh/security-alerts.md", "key": "brianespinosa/dotfiles/.claude/commands/gh/security-alerts.md" } } }

security-alerts

About

Step 1 — Detect context

Step 2 — Run

Step 3 — Display

Install security-alerts 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