Skip to content
Back to skills

Jev Model Router

ASecurity

Use `jev_route_model` when more than one available model could perform the task and the choice materially affects quality, cost, or latency.

  • 17 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 5, 2026
code-quality

Security analysis

A100/100

Scanned October 5, 2026

npx -y skills add tensology/decisionsai --skill jev-model-router --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jev Model Router?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Jev Model Router
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tensology-jev-model-router/badge)](https://www.skillsdirectory.com/skills/tensology-jev-model-router)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# Jev Model Router

Use `jev_route_model` when more than one available model could perform the task and the choice materially affects quality, cost, or latency.

## Prepare the decision

1. Describe the task without including unrelated conversation history.
2. List only models the current environment can actually invoke.
3. Describe each model using known capabilities, relative cost, and relative latency. Do not invent benchmarks.
4. Order the decision priorities and include binding constraints.
5. Set stakes by the consequence of a wrong result.

Call `jev_route_model`, then use the selected model if it remains available and allowed. A high `escalate` value means the selected model should be paired with human review or a second independent check.

Routing is advisory. It does not authorize access to a model, increase budget, or weaken the task's existing verification requirements.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…