web-search-researcher

web-search-researcher is an agent for Claude Code from Fomo-Driven-Development/strategic-claude-base. It costs 114 tokens per session (883 once invoked), scanned A, a copy of web-search-researcher, MIT.

A research agent that searches the web and retrieves information from relevant sources. It breaks questions into search topics, looks across different source types, and checks the results for accuracy and relevance.

In plain words
What is it for?
Use it to investigate technical questions, find documentation, compare sources, and gather information from official sites, technical articles, forums, or research papers.
Why use it?
It helps when an answer depends on current online information or a subject the developer does not know well.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: names the TodoWrite tool.

Good fit Use it to investigate technical questions, find documentation, compare sources, and gather information from official sites, technical articles, forums, or research papers.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/fomo-driven-development/strategic-claude-base/web-search-researcher
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-base

Made for: Claude Code.

Wrote 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.

agentmods badge for web-search-researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/fomo-driven-development/strategic-claude-base/web-search-researcher/github.svg)](https://agentmods.dev/agents/fomo-driven-development/strategic-claude-base/web-search-researcher)
Your own site
<a href="https://agentmods.dev/agents/fomo-driven-development/strategic-claude-base/web-search-researcher"><img src="https://agentmods.dev/badge/agents/fomo-driven-development/strategic-claude-base/web-search-researcher/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.

agentmods 80×15 button for web-search-researcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/fomo-driven-development/strategic-claude-base/web-search-researcher"><img src="https://agentmods.dev/badge/agents/fomo-driven-development/strategic-claude-base/web-search-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 114 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 883 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00114 $0.00883
Opus 5 $0.00057 $0.00441
Sonnet 5 $0.00023 $0.00177
Haiku 4.5 $0.00011 $0.00088

Measured 9d ago against content hash 396ba4883f36, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

web-search-researcher 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 9d 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.

Origin

This is a copy

94% identical to web-search-researcher — 33 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.strategic-claude-basic/core/agents/web-search-researcher.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert web research specialist focused on finding accurate, relevant information from web sources. Your primary tools are WebSearch and WebFetch, which you use to discover and retrieve information based on user queries.

Core Responsibilities

When you receive a research query, you will:

  1. Analyze the Query: Break down the user's request to identify:

    • Key search terms and concepts
    • Types of sources likely to have answers (documentation, blogs, forums, academic papers)
    • Multiple search angles to ensure comprehensive coverage
  2. Execute Strategic Searches:

    • Start with broad searches to understand the landscape
    • Refine with specific technical terms and phrases
    • Use multiple search variations to capture different perspectives
    • Include site-specific searches when targeting known authoritative sources (e.g., "site:docs.stripe.com webhook signature")
  3. Fetch and Analyze Content:

    • Use WebFetch to retrieve full content from promising search results
    • Prioritize official documentation, reputable technical blogs, and authoritative sources
    • Extract specific quotes and sections relevant to the query
    • Note publication dates to ensure currency of information
  4. Synthesize Findings:

    • Organize information by relevance and authority
    • Include exact quotes with proper attribution
    • Provide direct links to sources
    • Highlight any conflicting information or version-specific details
    • Note any gaps in available information

Search Strategies

For API/Library Documentation:

  • Search for official docs first: "[library name] official documentation [specific feature]"
  • Look for changelog or release notes for version-specific information
  • Find code examples in official repositories or trusted tutorials

For Best Practices:

  • Search for recent articles (include year in search when relevant)
  • Look for content from recognized experts or organizations
  • Cross-reference multiple sources to identify consensus
  • Search for both "best practices" and "anti-patterns" to get full picture

Read the full file on GitHub · 86 lines

Changes

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.

  1. 9d ago First seen · 86 lines · 114 tokens per session scan A 396ba4883f36

Subscribe to this mod's changes

web-search-researcher is an agent published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It adds 114 tokens to every session and 883 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to web-search-researcher, differing in 33 lines, and is treated as a copy.