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/axgord/claude-workflow/web-readingnpx skills add AxGord/claude-workflow --skill web-readinggit clone --depth 1 https://github.com/AxGord/claude-workflowWrote 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/axgord/claude-workflow/web-reading)<a href="https://agentmods.dev/skills/axgord/claude-workflow/web-reading"><img src="https://agentmods.dev/badge/skills/axgord/claude-workflow/web-reading.svg" alt="Measured on agentmods" 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.00009 | $0.00613 |
| Opus 5 | $0.00005 | $0.00307 |
| Sonnet 5 | $0.00002 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
web-reading 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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal: protect main context from web content bloat
Every web fetch goes through a subagent (Agent tool) with a precise extraction prompt — ALWAYS specify exactly what to extract, never "get the page content" or "summarize this page". Never put raw web content into main conversation context.
Subagents run in the background by default — pass
run_in_background: false when the fetched result gates your next step.
Note: WebFetch/WebSearch may be deferred tools — load them via
ToolSearch (select:WebFetch,WebSearch) before first use.
Step 1: Source-specific tools (no fetch needed)
Pick the right tool before reaching for the web:
- GitHub repos/issues/PRs →
ghCLI - GitHub raw file URLs (.md, .json, .yaml, .txt, etc.) →
gh apior direct WebFetch - npm packages →
npm info <pkg> - PyPI packages →
pip index versions <pkg>or the PyPI JSON API (https://pypi.org/pypi/<pkg>/json) —pip showonly reports the locally installed version, not what's available - Local files → Read tool
If none apply → Step 2.
Step 2: Direct WebFetch via subagent
Subagent uses WebFetch with a strict prompt:
"Extract ONLY the main article content as clean markdown. Ignore navigation, sidebars, headers, footers, ads, cookie banners. Return structured content with headings, code blocks, and lists."
Use WebFetch for raw files too (.md, .json, .yaml, .txt, .xml, .csv).
Step 3: Jina Reader fallback (HTML pages only)
If WebFetch failed or returned junk (bot walls, heavily scripted pages), Jina converts HTML → clean markdown:
https://r.jina.ai/<original-url>
- HTML pages ONLY — never raw files (Step 2 handles those)
- NEVER route URLs containing tokens, secrets, or signed parameters through r.jina.ai — it is a third-party service and sees the full URL
Step 4: WebSearch
If the page itself is inaccessible — search for the same content in mirrors, official docs, blogs, cached versions.
Step 5: Browser MCP, if available (last resort)
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.
- 5d ago First seen · 71 lines · 9 tokens per session scan A d53b178a2691
web-reading is a skill published in the GitHub repository AxGord/claude-workflow (5 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 613 once invoked, about $0.0000 per session on Opus 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-08-31.
Other skills, from other repositories
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.