REPOSITORY ANALYSIS

jev-model-router

A community Claude Code Templates mod that uses Jev to suggest subagent models and reasoning levels.

E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
Stars
31,561
Forks
3,585
License
MIT
Last commit
2026-09-24

What Jev does here

Evaluates task tier, reasoning needs and production risk; local policy maps results to invocation settings.

Makes routing rules and per-request choices explicit and configurable.

A davila7 community project, not an official Anthropic repository or mod. Aggregate savings and safety effects were not verified here.

What task does this project fit?

Route a coding task to a configured model tier and reasoning effort.

Material analysed:

From input to action

  1. Send task context with capability and effort questions.
  2. Normalize native TypeSafe or Gateway answers.
  3. Map judgments through local model/effort policy before invoking the coding agent.

Implementation details that matter

Provider answer shapes are different

jev-spike.mjs explicitly contrasts native noul/confidence with Gateway boolean/probabilities. Its confidenceOf helper derives a maximum probability only when a native confidence field is absent.

Inspect the supporting source ↗

Routing policy remains local

The module combines tier and reasoning-demand results with configured mappings. The example model identifiers and thresholds are a routing policy, not proof that a tier can solve a given repository task.

Inspect the supporting source ↗

When to choose it

Use it to make routing choices inspectable and configurable. Measure final task success and total cost, including misroutes, before accepting savings claims.

How to inspect it yourself

Compare the two provider adapters and their confidence/risk readers, then inspect jev-model-router.ts for how each outcome selects model and effort.

Limits of this review

  • No Claude Code routing run or cost benchmark was performed.
  • Provider SDK changes can alter response metadata; the reviewed commit is fixed.
Primary material used in this analysis