# Plan RouterBase Model Routing

Teams need current model choices without chasing changing provider catalogs. This skill turns RouterBase catalog checks into routing plans with fallbacks, validation steps, and cost notes.

## Install

```bash
npx skillstore add zenlee123/routerbase-model-routing
```

## Metadata

- Status: approved
- Slug: zenlee123-routerbase-model-routing
- Skillstore revision: r1
- Version status: missing
- Tree hash: 9e073f63c9b96c3c17535a33d37a2ae885837d535c60d52b16b4f14b95e6a05f
- Author: zenlee123
- GitHub username: zenlee123
- License: MIT
- Repository: https://github.com/zenlee123/routerbase-agent-skills/tree/main/skills/routerbase-model-routing
- Ref: 6dab19906b1e4121c46ce2353d0b5a559b20657c
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, env\_access, external\_commands
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/zenlee123-routerbase-model-routing
- Manifest: https://skillstore.pages.dev/api/skills/zenlee123-routerbase-model-routing/manifest

## Capabilities

- Classifies workloads by modality, constraints, and required model features.
- Guides live RouterBase catalog and pricing checks when credentials are available.
- Suggests primary and fallback models with validation tests and caveats.
- Documents routing decisions in a repeatable table format.
- Highlights retry rules for transient errors and nonretryable request failures.
- Separates chat, image, video, audio, and embeddings routing considerations.

## Use Cases

- Select a chat routing plan: Choose a primary chat model, fallback model, and validation test for a new assistant.
- Control inference costs: Compare model options against price ceilings, latency targets, and quality needs before launch.
- Document platform routing: Create a clear routing table with assumptions, caveats, and checks for production readiness.

## Prompt Templates

### Choose a Starter Model

```
Recommend a RouterBase primary model and fallback for a chat assistant. Ask for any missing constraints before finalizing the plan.
```

### Compare Cost and Latency

```
Compare RouterBase model options for this workload: [describe workload]. Prioritize latency, price ceiling, context length, and validation steps.
```

### Design Multimodal Routing

```
Design RouterBase routing for chat plus [image, video, audio, or embeddings]. Separate endpoints, fallback choices, and feature assumptions.
```

### Create a Production Routing Review

```
Audit this RouterBase routing plan for reliability, fallback compatibility, retry rules, cost checks, and missing production validation.
```

## Limitations

- It does not guarantee current prices or model availability without a live catalog check.
- It does not replace production evaluation against your own prompts and latency targets.
- It cannot verify private account settings or smart routing configuration by itself.
- It assumes the user provides RouterBase credentials when live API calls are needed.

## Best Practices

- Query the live RouterBase catalog before final model recommendations.
- Validate tool calling, vision, JSON mode, streaming, and context length with real prompts.
- Keep fallback models compatible with the same request shape and user experience.

## Anti Patterns

- Treating published model examples as permanent source of truth.
- Retrying authentication, policy, validation, or malformed request failures without a configuration fix.
- Choosing fallbacks only by price while ignoring modality and feature compatibility.

## Security Audit

- Audited at: 2026-07-06T17:15:12.385\+00:00
- Summary: The static detections are documentation examples for RouterBase API calls, placeholder API-key usage, and Markdown code formatting. I found no evidence of credential exfiltration, unauthorized command execution, prompt injection, or suspicious intent in the reviewed files. Residual risk is limited to expected network/API-key use when users choose to query RouterBase.

## Stats

- Views: 1
- Downloads: 6
- Favorites: 0
- Popularity score: 0