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 Ce-Legend/ce-legend-skills --skill web-accessgit clone --depth 1 https://github.com/Ce-Legend/ce-legend-skillsWrote 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/ce-legend/ce-legend-skills/web-access)<a href="https://agentmods.dev/skills/ce-legend/ce-legend-skills/web-access"><img src="https://agentmods.dev/badge/skills/ce-legend/ce-legend-skills/web-access/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/ce-legend/ce-legend-skills/web-access"><img src="https://agentmods.dev/badge/skills/ce-legend/ce-legend-skills/web-access.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00173 | $0.01160 |
| Opus 5 | $0.00086 | $0.00580 |
| Sonnet 5 | $0.00035 | $0.00232 |
| Haiku 4.5 | $0.00017 | $0.00116 |
Grade A, and why
web-access 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Direct HTTP tools such as `curl`: status codes, headers, meta tags, raw HTML, JSON, JSON-LD, robots, sitemap, and minimal page probes. How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Access
Use this skill as Codex's external-world access layer. It closes the gap between model memory and live reality: current facts change, pages render through JavaScript, important evidence hides behind interaction, and some workflows only exist inside a logged-in browser session.
Treat web work as an evidence pipeline. Define the needed result, choose the lightest credible access layer, preserve source trails, escalate only when the page demands it, and stop when the requested outcome is verified.
What This Skill Protects Against
- stale answers from model memory when the facts may have changed
- weak research based on search snippets instead of opened sources
- losing source provenance, publication dates, timestamps, or page state
- overusing browser automation when a direct source read is enough
- underusing browser automation when content is rendered, interactive, or login-bound
- treating a clicked button, upload, download, or form submission as successful before verifying the resulting state
Core Workflow
-
Define the success condition. Decide whether the task needs a current fact, a primary-source answer, a completed web action, a downloaded artifact, a screenshot, or browser state verification.
-
Start with the lightest reliable layer. Use search and direct page reads for factual lookup. Use browser automation only when content is dynamic, interactive, gated by UI state, or depends on upload/download flows.
-
Escalate by evidence. If a page is incomplete, blocked, login-sensitive, JavaScript-rendered, or behaving differently from raw HTML, move to a browser layer instead of repeating the same failed fetch.
-
Return verifiable output. For research, cite sources and prefer primary material. For browser actions, report the exact completed state and any remaining uncertainty.
Tool Selection
Prefer this order unless the user request clearly starts at a higher layer:
- Built-in web/search tools: current facts, source discovery, page reading, finance/weather/sports lookups, and citation-backed answers.
- Playwright or in-app browser tools: clicking, typing, DOM inspection, screenshots, uploads, downloads, and JavaScript-heavy pages.
- Direct HTTP tools such as
curl: status codes, headers, meta tags, raw HTML, JSON, JSON-LD, robots, sitemap, and minimal page probes. - Local Chrome CDP fallback: tasks requiring the user's Chrome login state, regular browser profile behavior, or pages that fail in isolated browser contexts.
What ships with it
6 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.
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.
- 10d ago First seen · 92 lines · 173 tokens per session scan A 821b0eccf46b
web-access is a skill published in the GitHub repository Ce-Legend/ce-legend-skills (54 stars, last pushed yesterday), licensed MIT. It adds 173 tokens to every session and 1,160 once invoked, about $0.0009 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…