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 keysersoose/claude-code-setup --skill advanced-web-searchgit clone --depth 1 https://github.com/keysersoose/claude-code-setupWrote 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/keysersoose/claude-code-setup/advanced-web-search)<a href="https://agentmods.dev/skills/keysersoose/claude-code-setup/advanced-web-search"><img src="https://agentmods.dev/badge/skills/keysersoose/claude-code-setup/advanced-web-search.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.00082 | $0.01773 |
| Opus 5 | $0.00041 | $0.00886 |
| Sonnet 5 | $0.00016 | $0.00355 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
advanced-web-search 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 6d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advanced Web Search
Overview
Use this skill to discover high-quality candidate sources. Use the bundled OpenCLI Google backend by default for repeatable Google-operator discovery and saved JSON output. Other search, browser, HTTP, API, terminal, or MCP tools are fallbacks or verification aids. Search results are discovery leads, not evidence.
Core Workflow
- Clarify the search target, constraints, freshness needs, and source classes.
- Build several targeted query classes instead of one broad query.
- Use search operators where supported:
site:,filetype:,after:,before:, quoted phrases, booleanOR, exclusions,intitle:,inurl:, andintext:. - Run broad, primary-source, technical/paper/code, community, risk/counter-evidence, and recent-update queries as relevant.
- Triage candidate URLs by source type, credibility, relevance, date, and extraction feasibility.
- Hand off the selected source list to direct fetching, crawling, browser inspection, or the
deep-researchskill if synthesis is needed.
Required Search Tool
For repeatable source discovery, use the OpenCLI Google backend by default. Do not use a harness built-in web search as the primary discovery step for deep research when this script is available. Do not rely on terminal JSON redirection; always pass --output <path> so the result file is UTF-8 JSON and can be handed to deep-research.
python scripts/opencli_google_search.py \
--query "Hermes Agent NousResearch site:github.com" \
--max-results 20 \
--pages 6 \
--output outputs/hermes_agent_sources.json
Files:
scripts/opencli_google_search.py- default Advanced Web Search backend. It uses OpenCLI's browser bridge to render Google in Chrome, supports Google operators andstart=pagination, deduplicates canonical URLs, and writes clean JSON for any website with best-effort site metadata for common social, news, code, official, and research domains.scripts/opencli_network_probe.py- optional: scores likely JSON/list endpoints behind a dynamic page. Usage inreferences/dynamic-page-loading.md.scripts/opencli_api_paginate.py- optional: paginates a probe-found JSON endpoint in Chrome with cookies. Usage inreferences/dynamic-page-loading.md.scripts/google_opencli_x_search.py- Google result pagination through OpenCLI's logged-in Chrome bridge for X/Twitter result discovery. Use when raw Google HTML is blocked or when you need clean X post JSON with canonical URL, title, approximate likes, and X snowflake timestamp.scripts/operator_registry.py- operator parsing, validation, and query construction.scripts/test_opencli_google_search.py- offline tests for the default OpenCLI Google backend.
What ships with it
12 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 219 B
- references/dynamic-page-loading.md 3.2 KB
- references/opencli-google-backend.md 5.5 KB
- references/operator-guide.md 2.2 KB
- scripts/__init__.py 221 B runs code
- scripts/__pycache__/opencli_google_search.cpython-310.pyc 25 KB
- scripts/google_opencli_x_search.py 12 KB runs code
- scripts/opencli_api_paginate.py 9.3 KB runs code
- scripts/opencli_google_search.py 29 KB runs code
- scripts/opencli_network_probe.py 7.1 KB runs code
- scripts/operator_registry.py 8.4 KB runs code
- scripts/test_opencli_google_search.py 15 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.
- 6d ago First seen · 137 lines · 82 tokens per session scan A fe680f6bc55d
advanced-web-search is a skill published in the GitHub repository keysersoose/claude-code-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 1,773 once invoked, about $0.0004 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
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…