spark: Agent for Claude Code

.claude/agents/web-search-researcher.md

web-search-researcher is an agent for Claude Code from buildonspark/spark. It costs 114 tokens per session (995 once invoked), scanned A, a copy of web-search-researcher, Apache-2.0.

A research assistant that searches the web and retrieves source material to answer technical questions. It looks across search angles and favors official or reputable sources.

In plain words
What is it for?
Use it to investigate technologies, documentation, implementation options, and other questions that need web research.
Why use it?
It reduces the time spent finding current, reliable information when the answer is not clear from existing knowledge.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; names the TodoWrite tool.

This is buildonspark/spark's own configuration. It tells Claude Code how to work on spark itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spark configures →

Part of the spark plugin — 3 skills, 15 commands, 6 agents, 3 hooks shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to buildonspark/spark. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/buildonspark/spark/main/.claude/agents/web-search-researcher.md
Clone the repo
git clone --depth 1 https://github.com/buildonspark/spark

Made for: Claude Code.

Or install spark, the plugin that ships this one along with the rest of its 3 skills, 15 commands, 6 agents, 3 hooks.

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/buildonspark/spark/web-search-researcher/github.svg)](https://agentmods.dev/agents/buildonspark/spark/web-search-researcher)
Your own site
<a href="https://agentmods.dev/agents/buildonspark/spark/web-search-researcher"><img src="https://agentmods.dev/badge/agents/buildonspark/spark/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/buildonspark/spark/web-search-researcher"><img src="https://agentmods.dev/badge/agents/buildonspark/spark/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 995 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 92% 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.00995
Opus 5 $0.00057 $0.00498
Sonnet 5 $0.00023 $0.00199
Haiku 4.5 $0.00011 $0.00100

Measured 8d ago against content hash ecf3dd1a37b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 8d 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

92% identical to web-search-researcher — 26 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.

.claude/agents/web-search-researcher.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 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 · 109 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. 8d ago First seen · 109 lines · 114 tokens per session scan A ecf3dd1a37b0

Subscribe to this mod's changes

web-search-researcher is an agent published in the GitHub repository buildonspark/spark (110 stars, last pushed 10d ago), licensed Apache-2.0. It adds 114 tokens to every session and 995 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to web-search-researcher, differing in 26 lines, and is treated as a copy.