jev-kit uses Jev as a judge to cut Claude Code spend 233x
The open-source jev-kit uses Jev as a judge rather than a writer, blocking overly expensive sub-agent dispatches and tool calls, completing 9 of 9 browser tasks while cutting Claude spend 233x.
MY AGENTS WERE PAYING OPUS PRICES TO FIND A FILE. ONE OPEN-SOURCE KIT CAUGHT IT same 9 out of 9 browser tasks done. 233x less spent on claude per run it’s called jev-kit. it puts JEV next to CLAUDE CODE as a judge, not a worker. jev can’t write a single word. it answers yes/no, picks one option or gives a score, in about 0.3 seconds claude keeps the hard part. jev checks who you’re paying for the easy part who does what: → CLAUDE CODE writes, designs and fixes. the thinking stays here → TIER GUARD: before every sub-agent dispatch, jev asks “is this seat more expensive than the job?” the ladder: scout-find → scout → workerS → workerO → claude → fable. 2+ rungs too pricey = blocked. it never moves a job up → FABLE only gets a job after something cheaper already failed → BELAY: an agent says “done” without checking its work → sent back → AIRLOCK: watches every tool call. most pass a free code filter, only the unclear ones go to jev: allow, warn, rewrite or block → BROWSER AGENT: jev picks every click, claude only types into the fields the part i trust: it’s honest about itself → tier guard: 56 of 57 calls right on their evals → false denies on labelled cases: 0 → the 233x is claude spend only, over 27 runs, and the readme calls it directional → no TypeSafe key? it still installs, fails open and runs the code rules only a fund doesn’t send its PM to fetch coffee. your agent stack does it all day and bills you for it start in shadow mode. it logs what it would have blocked and blocks nothing. read that log for a week, then flip to enforce linux and wsl2 are supported, mac is untested. it’s a small new repo, so read the code before you wire it in paste this into claude code ↓ “Clone ~/code/jev-kit. Read the README and docs/install.md. Run install/install.sh --check-only and show me the plan. Map the tier guard ladder to my agents in ~/.claude/agents. Keep Airlock in shadow mode. Don’t wire settings.json and don’t touch my API key, I’ll put it in ~/.config/jev-kit/env myself. Nothing installs until I say go.” most agent bills aren’t hard problems. they’re easy jobs sitting in the wrong seat
This post quotes another post: x.com/xinc3s/status/2108204467774509059