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 agentmods add skills/code-yeongyu/lazycodex/ultimate-browsingnpx skills add code-yeongyu/lazycodex --skill ultimate-browsinggit clone --depth 1 https://github.com/code-yeongyu/lazycodexWhat 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 | $0.00260 | $0.02622 |
| Opus 5 | $0.00130 | $0.01311 |
| Sonnet 5 | $0.00052 | $0.00524 |
| Haiku 4.5 | $0.00026 | $0.00262 |
Grade A, and why
ultimate-browsing scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://r.jina.ai/https://weibo.com/<uid>/<pid>" # weibo via Jina How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultimate Browsing
Escalation web access for tasks a normal browse or fetch cannot complete. Reach for this skill the moment a page is blocked (WAF / 403 / Cloudflare), needs JS rendering, hides behind a login, or lives on a platform a generic fetcher cannot read. Escalate only when the cheaper tier cannot do the job:
Tier 1 — insane-search (headless extraction + WAF bypass) -> Tier 1.5 — agent-reach (platform-native APIs, esp. Chinese platforms) -> Tier 2 — Chrome stealth (real interaction via CloakBrowser + agent-browser).
PHASE 0 — ROUTE FIRST (MANDATORY)
User request
|
+- extract text/data from a URL --------------------- TIER 1 insane-search
+- URL blocked / 403 / Cloudflare / WAF ------------- TIER 1 insane-search
+- YouTube/Vimeo/TikTok subtitles or metadata ------- TIER 1 insane-search (yt-dlp)
+- read an article / blog / Reddit / HN / arXiv ----- TIER 1 insane-search
|
+- Chinese platform (xhs/douyin/weibo/bilibili/v2ex/wechat) TIER 1.5 agent-reach
+- podcast transcript / stock forum ----------------- TIER 1.5 agent-reach
+- Twitter feed / LinkedIn profile / GitHub via CLI - TIER 1.5 agent-reach
|
+- Tier 1/1.5 returned empty or partial ------------- TIER 2 Chrome stealth
+- click / fill form / scroll / interact ------------ TIER 2 Chrome stealth
+- screenshot / render / play video ----------------- TIER 2 Chrome stealth
+- login session across pages / inject cookies ------ TIER 2 Chrome stealth
+- test web app / QA / dogfood ---------------------- TIER 2 Chrome stealth
|
+- simple search query ------------------------------ NOT this skill (use web-search)
Read the matching reference before acting: references/insane-search/README.md, references/agent-reach/README.md, or references/chrome-stealth.md.
Tier 1 — insane-search (headless extraction)
When: content extraction, blocked-URL bypass, media metadata — no browser UI needed.
Why first: ~10x faster than a browser, no process spin-up; handles most "fetch this blocked page" requests via curl_cffi TLS impersonation, yt-dlp (1858 sites), Jina Reader, official public APIs, mobile URL transforms, and a Playwright real-Chrome fallback. The engine lives inside this skill at engine/ and is invoked as a module.
What ships with it
45 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 52 B
- ATTRIBUTION.md 4.9 KB
- engine/__init__.py 668 B runs code
- engine/__main__.py 4.3 KB runs code
- engine/bias_check.py 6.6 KB runs code
- engine/curl_probe.py 2.4 KB runs code
- engine/executor.py 6.3 KB runs code
- engine/fetch_chain.py 11 KB runs code
- engine/referers.py 327 B runs code
- engine/result_schema.py 1.1 KB runs code
- engine/summary.py 1.2 KB runs code
- engine/templates/package.json 331 B
- engine/templates/playwright_mobile_chrome.js 3.4 KB runs code
- engine/templates/playwright_real_chrome.js 5.4 KB runs code
- engine/tests/test_fetch_chain.py 2.7 KB runs code
- engine/tests/test_playwright_templates.py 11 KB runs code
- engine/url_transforms.py 3.2 KB runs code
- engine/validators.py 7.4 KB runs code
- engine/waf_detector.py 6.9 KB runs code
- engine/waf_profiles.yaml 5.6 KB
- references/agent-reach/career.md 712 B
- references/agent-reach/dev.md 1.3 KB
- references/agent-reach/README.md 2.2 KB
- references/agent-reach/search.md 821 B
- references/agent-reach/social.md 5.6 KB
- references/agent-reach/video.md 2.7 KB
- references/agent-reach/web.md 1.9 KB
- references/chrome-stealth.md 6.3 KB
- references/insane-search/cache-archive.md 2.6 KB
- references/insane-search/fallback.md 6.0 KB
- references/insane-search/jina.md 3.3 KB
- references/insane-search/json-api.md 3.5 KB
- references/insane-search/media.md 3.5 KB
- references/insane-search/metadata.md 2.9 KB
- references/insane-search/naver.md 3.3 KB
- references/insane-search/playwright.md 6.0 KB
- references/insane-search/public-api.md 3.4 KB
- references/insane-search/README.md 19 KB
- references/insane-search/rss.md 2.9 KB
- references/insane-search/tls-impersonate.md 6.3 KB
- references/insane-search/twitter.md 3.3 KB
- scripts/cookie_crypto.py 2.9 KB runs code
- scripts/cookie_domains.py 1.1 KB runs code
- scripts/cookie_paths.py 3.8 KB runs code
- scripts/extract_cookies.py 9.2 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.
- yesterday First seen · 141 lines · 260 tokens per session scan A b3d974e28376
ultimate-browsing is a skill published in the GitHub repository code-yeongyu/lazycodex (3,350 stars, last pushed 23d ago), licensed MIT. It adds 260 tokens to every session and 2,622 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…