HunterAlphaHub
OpenRouter model reference Facts from the public catalogue, dated and labelled
Jev Laya Verified
2026-10-10

GitHub · Browser agents · Tools and apps

wy-coliney/jev-browser-use

The cheapest way to see the drive-with-Jev, verify-with-an-LLM split in a browser.

What it does

A browser skill that splits the loop in two: Jev owns clicking, toggling, scrolling and navigation, while Codex keeps text input, visual judgment and the final verification. The README claims 5–10x faster browser operations in the author's own product workflows at EZCollegeApp.

The repository's own description: “5–10x faster browser operations: Jev clicks, Codex thinks and verifies. Built at EZCollegeApp.”

How it works

Shipped as a skill rather than a library — plugin.json plus a skills/ directory and an INSTALL.md — so it attaches to a browser connection that already exists instead of bundling a driver. That is what lets the README promise no extra driver and no npm dependencies.

The repository, by the numbers

Stars
1,021
Licence
MIT
Stack
JavaScript, shipped as an agent skill (plugin.json + skills/)
Last push
2026-09-23

Read from the GitHub API on 2026-10-09. Stars and the last push move daily — quote them with the date, the way we do.

What we checked

  • the README: the "Jev clicks. Codex thinks and verifies." split, the 5–10x claim scoped to EZCollegeApp, and the no-extra-driver line
  • the repository layout: plugin.json, skills/, INSTALL.md, scripts/, assets/
  • GitHub metadata on 2026-10-09: MIT, 1,024 stars, last push 2026-09-23

What we did not check. We did not install the skill or measure anything; the speed range is the author's own workflow measurement.

Open the repository ↗All builds

Send us a link

A project built with Jev, a post, a video, a correction, a tip. We open the link, check it says what you said it says, and write the entry ourselves.

Required a link, and an email to reply to. Optional everything else.

Add context — all optional

One or two sentences about what it does, in your words. We write the entry ourselves.

Cost, latency, a benchmark — anything you measured. We attribute these to you.

We store what you type and email it to ourselves. No IP address, no user agent, no referrer — the same rule as the mailing list.

What happens to what you send →