Route work between coding agents

Editorial kit referencing nidhi-singh02/agent-router. Useful for learning Score plus Choice composition. Quota impact and routing quality have not been independently measured.

Read source

What you'll make

Route a coding task to one of a few agents using Score and Choice.

A routing sketch with explicit constraints. Not a verified production router.

Jev decides

Scores or chooses among named agents given task state.

Your code acts

Your orchestrator actually invokes the selected agent and enforces quotas.

Agent prompt

Give your agent a useful brief.

Key-safe by design

Codex prompt

You are helping a developer prototype a Jev-powered application.

Goal: Prototype a quota-aware agent router with Jev Choice/Score and a deterministic fallback.

Product truth:
- Jev (TypeSafe System One) returns typed decisions and calibrated probabilities. It does not write emails, generate UI copy, play games by emitting pixels, or call Zapier.
- Your job is to write application code. Jev only answers questions whose possible answers are defined in advance.
- Use the official JS SDK documented at https://github.com/typesafe-ai/typesafe-sdk-js. Read the current README before inventing method names.
- Keep API keys in server-only environment variables. Never put TYPESAFE_API_KEY in client code, screenshots, git, or logs.
- Ship a working mock adapter first. Live TypeSafe calls are optional and must be clearly labeled.

Required behavior:
1. Inspect the current project and only change what is needed.
2. Define a small typed Choice or Score schema. Include an explicit uncertain / human-review path.
3. Implement mock mode with fixtures that include ordinary, ambiguous, and conflicting examples.
4. Add a server-only adapter that calls TypeSafe only when TYPESAFE_API_KEY is present.
5. Application code must validate the typed response and decide the action. Failed provider calls must not trigger side effects.
6. Do not send, delete, archive, or mutate real user accounts in this first version.
7. Add tests for the schema and mock path. Report what was run and what remains untested.

Official source to read: https://github.com/typesafe-ai/typesafe-sdk-js

Add tests for budget-exhausted fallback.

When finished, write a short Verification section distinguishing mock results from any live API call.

Copies instructions into your clipboard. It does not run or install anything.

Setup and guardrails

Start small. Keep the boundary clear.

Prerequisites

Named downstream agents
A quota or cost budget you define

Setup steps

List candidate agents and disallowed combinations.
Put budget remaining in state.
Never let the model raise its own quota.

Mock mode

Fixed routing table.

Live mode

Jev chooses; you still cap spend in code.