⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
jev-browser-use
Use when driving a web page in a browser — clicking, typing, navigating, logged-in or JS-rendered pages. Jev picks each step from the elements observed, under a host allowlist and a step budget.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Hermes Jev Skills
Give your agent a fast, cheap second brain for the small decisions.
Your agent burns frontier-model tokens on things that are not thinking: which model should answer this turn, which of 377 skills to load, which retrieved passages matter, which turns survive a summary, which button comes next. Those are decisions, not prose. Hand them to something that costs a fraction of a cent and answers in about 0.4 seconds, and let the expensive model do the writing.
That is what Jev is. It is TypeSafe's decision model. It never writes text. You give it a state and typed questions (pick one, score this, yes or no) and it answers with a calibrated confidence. This repo wires that into an agent's day.
jev dashboard. The profiles, paths and decisions here are a demo home; the pools are a real working set. python3 scripts/demo_home.py builds a home where nothing is real, which is where the next one comes from. One switch for Jev routing, every pool as a tier-by-work-kind grid, and each decision as it happens (tier, work kind, model, which pool it came from, confidence, latency).
What Jev decides, and what it costs
| Skill | What Jev decides | Measured |
|---|---|---|
| Model routing | Which model is good enough for this turn, from every model you can call | ~0.4 s per turn |
| Search | Which of the results you fetched are worth opening, whether the evidence answers the question, and which of your candidate queries to run next. Jev never writes a query | ~1.9 s per round (median of five live runs, two requests: rank, then sufficiency and the pick) |
| Social research | Which discovered posts are worth opening and, after a local evidence-floor check, whether a bounded projection answers the question. Depth and source linkage are enforced locally, not by Jev | Reuses jev search; no social-specific benchmark yet |
| Memory | Which retrieved passages are worth reading, and which contain hidden instructions | 60 passages per request, up to 480 per call; an injection screen runs locally even when Jev is down |
| Web screening (Hermes) | Which parts of a web_search / web_extract result carry instructions aimed at the agent, withheld before the agent reads them | In-distribution planted attacks in 80 real web results: 70 of 79 caught, against 11 for Hermes's own pattern scan; 0 of 1,520 clean chunks withheld; ~0.2 s per result. Not portable recall (scorecard, public transfer evidence) |
| Handoffs | Nothing, by default. We measured it: a handoff written from Jev's keep / summarize / drop digest recalled less than one written from the plain transcript. What ships is the whole dialogue, 1,200 words and a way back to the old session | 58.7% recall alone, 75.0% with one search, against 37.5% and 68.3% before (scorecard) |
| Choosing turns | Which turns to keep when a transcript must be cut to a fixed size | 71 turns in 0.95 s; beat choosing by recency 11 questions to 4 |
| Skill selection | Which installed skill this turn needs, or none | 377 skills in ~2.8 s; acknowledgements answered locally for free |
| Triage | How urgent a message is, what kind it is, and whether a person must see it | ~0.4 s per message, $0.00006 |
| Mailbox sorting | Which lane an inbox message belongs in — needs reply, updates, promotional, sales, spam — and whether it is worth a person's attention | ~0.44 s p50 per message, $0.00002 each |
| Computer use | The next GUI action, from a table of actions you already judged safe. --plan splits a multi-step command once, up front | ~0.5 s per decision |
| Browser use | The next page action, same contract | ~0.4 s per step |
Eleven skills ship as plain SKILL.md files, so they are not Hermes-only. The same folder works in Claude Code, Codex, or anything that reads a skill file.
jev mail --file inbox.json # sort a mailbox into lanes
jev mail --file inbox.json --summary # counts per lane, what was unsure, what it cost
Try it in two commands
git clone https://github.com/kerpopule/hermes-jev-skills ~/hermes-jev-skills && python3 ~/hermes-jev-skills/install.py
jev setup-key # paste your key into the one-time page it opens, then run: jev doctor
Python 3.9 or newer, no dependencies. Got it as a zip? Unzip it anywhere and run python3 install.py from that folder. Or point your agent at this repo and say "install Hermes Jev Skills": it will follow AGENTS.md.
The installer finds Hermes, Claude Code and Codex on the machine and installs for each one it finds. python3 install.py --check shows exactly what it would do without changing anything. --uninstall reverses it. For Claude Code it also adds four lane subagents (jev-lane-small … jev-lane-escalate, each with its own model and effort) and a short, delimited lanes block in ~/.claude/CLAUDE.md, backed up first (--no-claude-md leaves that file alone). See lanes.md.
Not sure yet? Run jev models suggest --write to draft routing pools from price bands, then /jev routing shadow for a day. Shadow mode decides and logs without switching anything, so a day of decisions costs almost nothing and risks nothing. Turn it on when the log looks right.
On Hermes
Built for Hermes. The dashboard has its own notes in router-dashboard/README.md.
Start in shadow mode. It is the honest way to see what Jev would do before it does anything.
/jev status
/jev routing shadow decide and log, do not switch (start here)
/jev routing on switch models per turn
/jev skills on suggest the right skill per turn
/jev notice on show "[Jev] hard · coding → kimi-k3 · confidence 0.92" on routed replies
/jev screen shadow screen web_search / web_extract results for injected instructions, log only
/jev screen on withhold the parts that carry them, with a notice in their place
/jev routing on all make it the default for every profile (a profile's own setting still wins)
The agent gets five tools: jev_memory_filter, jev_compact_select, jev_choose_action, jev_supervise, jev_escalate.
The hermes-jev plugin uses only public plugin seams (pre_llm_call, transform_tool_result, the llm_request middleware, tools, a slash command), so hermes update does not break it and nothing in Hermes core is patched.
A plugin can swap the model, not the provider connection. On OpenRouter that still covers every vendor. If you run /model yourself, your choice wins.
Every model you have
jev models list # everything this machine can call: price, context, vision, reasoning
jev models providers # which providers you hold a key or login for
jev models suggest --write # first-draft pools from price bands; then edit to taste
The catalog is models.dev, filtered to providers whose API-key name is set in your environment or Hermes .env, or that Hermes holds a login for. Only key names are read. Pools live in ~/.hermes/jev/routing.json (the default for every profile); ~/.hermes/profiles/<name>/jev/routing.json overrides it for one profile. Details in skills/jev-model-routing.
Your API key never touches the agent
jev setup-key opens a one-time page served only by your own computer. You paste your TypeSafe key there. It goes straight into the OS secret store (macOS Keychain, or secret-tool on Li
// HOW IT'S BUILT
KEY FILES