Skip to main content
Agent skill

Omni Models

Query available AI models across all configured providers. List models, resolve model aliases, and browse the full model catalog including provider-specific variants.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Omni Models when an AI agent needs a reusable SKILL.md workflow for this job: Query available AI models across all configured providers. List models, resolve model aliases, and browse the full model catalog including provider-specific variants.

When not to use it

Skip Omni Models when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/omni-models
# Save SKILL.md to ~/.claude/skills/omni-models/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/omni-models/SKILL.md. For a shared project, commit the folder at .claude/skills/omni-models/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Omni Models skill for this task: Use Omni Models when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

## Overview

Query available AI models across all configured providers. List models, resolve model aliases, and browse the full model catalog including provider-specific variants.

## Authentication

All requests require a valid Bearer token or session cookie. Obtain a token via `POST /api/auth/login` or configure `REQUIRE_API_KEY=false` for local development.

## Endpoints

### GET /api/v1/models

List available models

Returns all models available across configured providers. The discovery filters (`capability`, `min_context`, `kind`, `q`) are opt-in: without them the response is unchanged. They narrow the caller's own (key-filtered) catalog and run before `limit`/`after` paging.

```bash curl http://localhost:20128/api/v1/models \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### POST /api/v1/models/query

Query a model shortlist

Filtered shortlist over the same catalog as `GET /v1/models` (same auth and per-key visibility). Results are ordered by `owned_by`, then `id`, and capped by `limit` (default 20, maximum 100).

```bash curl -X POST http://localhost:20128/api/v1/models/query \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### GET /api/v1/models/health

Per-model pause state for the caller's key

Read-only liveness view over the in-memory model lockout store. `ok` means no pause observed by this instance (not a health verdict); connection-level pauses live outside the store read here. Additive: leaves GET /v1/models and its cache untouched. `retry_after` carries the shortest remaining lockout in seconds, rounded up, only when `state` is `cooling`. One documented difference from the dispatch 429 `model_cooldown` rule: a model with one lockout-covered connection and one connection-level cooldown still reads `cooling` here, while the 429 requires every connection to carry a model cooldown.

```bash curl http://localhost:20128/api/v1/models/health \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### GET /api/models

List models (management)

```bash curl http://localhost:20128/api/models \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### PUT /api/models/alias

Create or update a model alias

```bash curl -X PUT http://localhost:20128/api/models/alias \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### GET /api/models/catalog

Get full model catalog

```bash curl http://localhost:20128/api/models/catalog \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### GET /api/models/openrouter-catalog

GET models › openrouter catalog

```bash curl http://localhost:20128/api/models/openrouter-catalog \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

### POST /api/models/test

POST models › test

```bash curl -X POST http://localhost:20128/api/models/test \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### POST /api/models/test-all

POST models › test all

```bash curl -X POST http://localhost:20128/api/models/test-all \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```

### GET /api/v1/models/{model}

GET models › <model>

```bash curl http://localhost:20128/api/v1/models/{model} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```

## Payloads

See the full OpenAPI specification at `GET /api/openapi/spec` or `docs/openapi.yaml` for detailed request/response schemas.

Intended uses

  • Use Omni Models when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.