Jev directory
CommunityJev Agents & MCP
Jevify — Kevin-Zhouu
Claude Code and Codex skill that audits a codebase for LLM call sites, proposes which routing, classification, and rubric-scoring decisions to convert to Jev, and reports latency and cost comparisons after the scope is approved.
- Stars
- 4
- Reading time
- 2 min
- Published by
- Community
- Added
- Oct 2026
This is one of several Jev listings for the same project. The canonical entry is Jevify (investigation prompt).
Highlights
- Installs with npx skills add Kevin-Zhouu/jevify, then runs as /jevify in Claude Code or $jevify in Codex.
- Audits a codebase for LLM call sites and proposes routing, classification, and rubric-scoring decisions to convert.
- Scope options include a new branch, a separate copy, report only, or converting individual calls.
- Keeps free-form generation with your LLM and adds a fallback for uncertain decisions.
- Demo run: 12 questions, 136 lines of JSON; Jev 0.44s versus Claude Haiku 4.5 at 5.11s in one synthetic example.
Questions about this entry
Short answers drawn from the linked project or page.
Install with `npx skills add Kevin-Zhouu/jevify`. Then in Claude Code (beta) use `/jevify`, in Codex use `$jevify`, or say "jevify this repo." You can scope it to a path, for example `/jevify src/agents/triage.py`.
No. No key or setup questions are needed to see the plan. Live validation uses `TYPESAFE_API_KEY` or `OPENROUTER_API_KEY`; without a Jev key, the audit and approved code changes still work but live validation is skipped.
Decisions such as routing, classification, and rubric scoring are candidates for conversion. Free-form generation stays with your LLM, and you receive a conversion plan plus a results report.
The flow is audit first, then you approve scope and output before any conversion. You choose a new branch, a separate copy, report only, or individual calls. It keeps generation with your LLM, adds fallback for uncertain decisions, and runs tests.
Claude Code support is beta with known conversion validation failures, and full cross-harness re-evaluation is pending. Historical Codex DEV runs passed. The audit-first flow is described as new.
Skill helpers use Python's standard library. Development checks require Python 3.10+, Node 18+, and `npm ci` in the `eval/` directory, followed by the unittest discovery and freeze verification commands.
No. It is one synthetic example via OpenRouter, replayed from real stream timestamps: 12 questions, 136 lines of JSON, Jev at 0.44s and Claude Haiku 4.5 at 5.11s, with all 12 category choices matching. It is not a general benchmark.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
X: A usage router for Grok Bot
X: A prompt box that fills itself in
X: How Jev makes agents faster and cheaper
YouTube: CJ from Syntax demos browser use, classification, code review, a model router, and a chat bot with no LLM.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.