Hermes Jev Skills

What Hermes Jev Skills does

Jev is TypeSafe's decision model, and the README stresses that it never writes text. You give it a state and typed questions, such as pick one, score this or answer yes or no, and it replies with a calibrated confidence. This repository wires that into an agent's routine so the expensive model is left to do the writing. The README gives rough timings, for example about 0.4 seconds per model-routing turn and 377 skills scanned in about 2.8 seconds.

Eleven skills ship as plain SKILL.md files, including model routing, search, memory, web screening, choosing turns to keep, skill selection, triage, mailbox sorting, computer use and browser use. For web screening, the README reports that Jev caught 70 of 79 planted attacks in 80 real web results, against 11 for Hermes's own pattern scan. A jev dashboard shows each decision as it happens.

Key features

• Model routing that picks a good-enough model for each turn in about 0.4 seconds
• Skill selection across 377 installed skills in about 2.8 seconds
• Web screening that withholds instruction-bearing parts of web_search and web_extract results
• Memory skill that ranks retrieved passages and screens them for hidden instructions
• Triage and mailbox sorting for incoming messages
• Computer-use and browser-use skills that choose the next action from a table of actions you judged safe

When to use it

• Cutting frontier-model spend by routing simple turns to a cheaper model
• Screening fetched web pages for hidden instructions before the agent reads them
• Sorting an agent's inbox into lanes such as needs reply, updates and spam

Who it is for: Hermes Agent operators who want a cheap decision layer for routing, screening and skill selection.

How it fits with Hermes Agent

Built for Hermes agents, including a Hermes-specific web screening skill. Because the skills are plain SKILL.md files, the same folder also works in Claude Code and Codex.

Note: The skills depend on Jev, TypeSafe's decision model, although the README says the memory injection screen runs locally even when Jev is down.

FAQ