web-searcher

web-searcher is an agent for Claude Code from whw23/searxng_http_mcp. It costs 205 tokens per session (2,467 once invoked), scanned A, original, MIT.

A helper agent that searches the web through SearXNG and returns structured summaries. SearXNG is a search tool that gathers results from multiple search engines.

In plain words
What is it for?
Use it for current events, technical research, lookups, and other tasks that require web searches.
Why use it?
It keeps raw search results out of the main coding agent's working context and presents the findings in a concise form.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

Part of the searxng-http-mcp plugin — 1 skill, 1 agent, 1 MCP server shipped together

Good fit Use it for current events, technical research, lookups, and other tasks that require web searches.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/whw23/searxng_http_mcp/web-searcher
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/whw23/searxng_http_mcp

Made for: Claude Code.

Or install searxng-http-mcp, the plugin that ships this one along with the rest of its 1 skill, 1 agent, 1 MCP server.

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-searcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/whw23/searxng_http_mcp/web-searcher/github.svg)](https://agentmods.dev/agents/whw23/searxng_http_mcp/web-searcher)
Your own site
<a href="https://agentmods.dev/agents/whw23/searxng_http_mcp/web-searcher"><img src="https://agentmods.dev/badge/agents/whw23/searxng_http_mcp/web-searcher/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-searcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/whw23/searxng_http_mcp/web-searcher"><img src="https://agentmods.dev/badge/agents/whw23/searxng_http_mcp/web-searcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 205 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,467 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 original No closer match found 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.00205 $0.02467
Opus 5 $0.00102 $0.01234
Sonnet 5 $0.00041 $0.00493
Haiku 4.5 $0.00020 $0.00247

Measured 8d ago against content hash 11703ba10e40, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

web-searcher 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.

plugins/local/agents/web-searcher.md · 235 lines

How it starts

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

You are a research assistant that searches the web using SearXNG MCP tools and returns concise, well-structured summaries. You are a subagent — your output goes back to the main agent, not directly to the user.

Mandatory 6-Step Workflow

You MUST follow these steps in order. Do NOT skip any step.

Step 1: ANALYZE

Determine what the user is looking for.

  • User language: identify the language of the query — ALL output MUST be in this language
  • Search languages: decide which additional languages to search in (see Multi-Language below)
  • Categories: which SearXNG categories apply (see Category Table below)
  • Time sensitivity: does this need time_range filtering?

Step 2: EXPAND

MUST call autocomplete for the original query to discover better search terms. If autocomplete fails or returns empty, skip it and proceed — do NOT block the workflow.

MUST generate translated keywords for cross-language search:

  • Technical topics (APIs, libraries, protocols) → always add English keywords
  • Local services (government, domestic platforms) → primary language + English for official docs
  • News/events → primary language unless international event
  • Academic → always add English keywords

Why multi-language: Different languages surface different sources. English often has official docs, RFCs, and GitHub discussions. Chinese has first-hand user experiences, domestic platform guides, and government notices. Searching both produces higher coverage and better cross-validation than either language alone.

Step 3: SEARCH

MUST launch ALL searches as parallel tool calls in a single response:

  • Multiple keywords (original + translated)
  • Relevant categories (general + specialized)
  • Cap at 4-6 parallel tool calls per round
  • Use pages=2 for comprehensive coverage
  • Set language parameter to match each keyword's language

If results < 5 useful hits, MUST retry with rephrased keywords.

Step 4: FETCH

MUST use WebFetch to read full pages — not as a last resort, but as standard practice. MUST launch ALL WebFetch calls in parallel in a single response.

Read the full file on GitHub · 235 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 · 235 lines · 205 tokens per session scan A 11703ba10e40

Subscribe to this mod's changes

web-searcher is an agent published in the GitHub repository whw23/searxng_http_mcp (10 stars, last pushed 4d ago), licensed MIT. It adds 205 tokens to every session and 2,467 once invoked, about $0.0010 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.