LazyCodex is an agent harness for working on complex codebases, combining project memory, planning, execution, and completion checks inside Codex. It is for developers who want structured, repeatable assistance when handling substantial software projects. The catalogue contains the skills, hook, and MCP integration that provide its workflow inside Codex.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add code-yeongyu/lazycodex --skill browsergit clone --depth 1 https://github.com/code-yeongyu/lazycodexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/code-yeongyu/lazycodex/browser)<a href="https://agentmods.dev/skills/code-yeongyu/lazycodex/browser"><img src="https://agentmods.dev/badge/skills/code-yeongyu/lazycodex/browser/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/code-yeongyu/lazycodex/browser"><img src="https://agentmods.dev/badge/skills/code-yeongyu/lazycodex/browser.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00094 | $0.02071 |
| Opus 5.5 | $0.00038 | $0.00828 |
| Sonnet 5.5 | $0.00019 | $0.00414 |
| Haiku 4.5 | $0.00009 | $0.00207 |
Grade A, and why
browser scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser
One library, two engines. omowright ships inside this skill; choose the engine before you act:
| You need | Engine | Entry point |
|---|---|---|
| A site the user is signed into, their open tabs, a form, a click-through, a screenshot, web QA, an extension popup | attached — the user's own browser through BrowserSkill | connectBrowserSkill() |
| A throwaway profile, bot-scoring evasion, a CAPTCHA, network interception, a QA flight trace, coordinate control, headless runs | owned — a browser your code launches | connectPipe() / connectCloakProfile() — references/owned-engine/README.md |
| A 403/WAF host the attached engine cannot open, a platform with a native reader, an archive snapshot | neither | the ultimate-browsing skill |
Attached is the default, because it is the only engine carrying the user's logins and the only one where a human is a single call away. Never substitute one engine for the other silently: if the attached engine is not set up, run the onboarding script and tell the user its one remaining step.
Step 0 — which engine this session is allowed to use
When OMO_BROWSER_ENGINE is set (the OmO desktop app sets it for every session), it wins over the table above:
| Value | What you do |
|---|---|
connected |
Use connectBrowserSkill() only. If the user's browser is not connected you get a "Connect your browser" error: relay it and stop. Never open another browser |
builtin |
Do not call connectBrowserSkill(); use the app's in-app browser tools |
none |
Do not do browser work. Say that agent browser access is off for this project |
| unset | The table above, as before (terminal use) |
While any engine is set, loadOmowright() returns a guarded library. The owned engine (connectPipe,
connectCloakProfile, connect) and every other export that acts on a browser is refused, so the table above
does not apply: do not look for a way around it, and tell the user what the session allows. Under connected
the app sees what the browser is doing, and before a click, Enter or script that sends, posts, pays, orders,
subscribes, deletes or closes an account, and before Enter in a message box, it asks the user first. A "No" fails the action with
BrowserActionDeclinedError: report that, never retry it or go around it (session.tool() lets only reads
through; evaluate is guarded too). If the user presses Stop, the next call throws BrowserUserStoppedError: tell
the user browser use was stopped and start no new session this turn.
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 42 B
- ATTRIBUTION.md 1.8 KB
- references/commands.md 6.2 KB
- references/install.md 5.8 KB
- references/owned-engine/frames-and-humans.md 2.6 KB
- references/owned-engine/ladder.md 3.8 KB
- references/owned-engine/network.md 2.9 KB
- references/owned-engine/README.md 3.3 KB
- references/recipes/1password.md 2.6 KB
- references/remote.md 1.1 KB
- runtime/omowright/index.js 933 KB runs code
- runtime/omowright/manifest.json 347 B
- runtime/omowright/page-bundle.js 45 KB runs code
- scripts/browser-doctor.mjs 4.1 KB runs code
- scripts/browser-engine-guard.mjs 20 KB runs code
- scripts/browser-install.mjs 2.8 KB runs code
- scripts/omowright.mjs 1.8 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago Changed 76d063d0a112
- 12d ago Changed · +24 lines 8ffc0504459d
- 21d ago Changed · +7 lines e93740ad39c8
- 22d ago Changed · +13 lines · +5 tokens per session 1ed587a58522
- 23d ago First seen · 90 lines · 89 tokens per session scan A 46b69edd166d
browser is a skill published in the GitHub repository code-yeongyu/lazycodex (3,782 stars, last pushed 2d ago), licensed MIT. It adds 94 tokens to every session and 2,071 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-23.
Other skills, from other repositories
computer-use
Drives the GUI of a visible local app window through orca computer: accessibility tree, clicks, typing, menus, dialogs, and screenshots in native apps and external browser windows (Chrome, Edge, Safari) or webviews. Prefer a programmatic path (shell, filesystem, git, HTTP, existing CLIs) whenever it can complete the…
browser-use
Control the user's Chrome through the existing persistent Node REPL and the Qwen Browser SDK.
opencli-browser
Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers the selector-first target contract, compound form fields, stale-ref handling, network capture, and the agent-native envelopes the CLI returns. Not for writing…
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.