Who it is forA developer running a Hermes agent on a frontier model who wants lower token costs without losing answer quality.
The problemAgents spend frontier-model tokens on small routing decisions such as which model should answer this turn.
The outcomeEach turn is routed to a model Jev judges good enough, and a shadow log shows what it would have done before anything switches.
What you need first
- Python 3.9 or newer (no dependencies)
- A TypeSafe key from console.typesafe.ai
- Hermes, Claude Code or Codex installed on the machine (the installer finds them)
Steps
- Run
python3 install.pyfrom the cloned repo folder. - Run
jev setup-key, paste your key into the page it opens, then runjev doctor. - Run
jev models suggest --writeto draft routing pools from price bands. - In Hermes, run
/jev routing shadowand review the log for a day. - When the log looks right, run
/jev routing on.
Prompt for your agent
Install the hermes-jev-skills repo from kerpopule on this machine, set up the key, and run `jev models suggest --write`. Enable `/jev routing shadow` for the <profile> profile and report the decisions logged so far, with tier, model and confidence for each. Verify that no model switch happened while in shadow mode.
Caveat. A plugin can swap the model but not the provider connection, and the routing commands are for Hermes only.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page