A command that searches Markdown files collected from websites and shows useful text around the best matches. It can search all collected sources or one named source.

Use it to find information in Markdown fetched by the project's web-add or document-fetching tools, using a regular-expression search pattern.

A list of matching files or lines may not provide enough context to answer a question. This command reads the surrounding passages so the result is easier to use and verify.

web-search — Command for Claude Code by raintree-technology/docpull

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/raintree-technology/docpull

Made for: Claude Code.

Or install docpull, the plugin that ships this one along with the rest of its 1 skill, 10 commands, 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/raintree-technology/docpull/web-search/github.svg)](https://agentmods.dev/commands/raintree-technology/docpull/web-search)

Your own site

<a href="https://agentmods.dev/commands/raintree-technology/docpull/web-search"><img src="https://agentmods.dev/badge/commands/raintree-technology/docpull/web-search/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/raintree-technology/docpull/web-search"><img src="https://agentmods.dev/badge/commands/raintree-technology/docpull/web-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 651 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.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.00651
Opus 5.5	$0.00010	$0.00260
Sonnet 5.5	$0.00005	$0.00130
Haiku 4.5	$0.00002	$0.00065

Measured 1mo ago against content hash 8ce54b741ef0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

plugin/commands/web-search.md · 45 lines

How it starts

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

Search fetched web-source Markdown

The user wants to search Markdown that has already been pulled by /web-add (or ensure_docs). This composes two MCP tools: grep_docs finds matching files; read_doc pulls more context around the top hits so the answer is grounded, not just a list of file:line references.

User input: $ARGUMENTS

How to handle the input

Parse $ARGUMENTS as:

First whitespace-separated token = pattern (regex; can be quoted to include spaces).
Optional second token = source alias to restrict the search to one fetched source. Pass it as the library argument when calling grep_docs.

If empty: reply Usage: /web-search <pattern> [source]. Run /web-list to see what's cached. and stop.

Workflow

Find candidates. Call grep_docs(pattern=<pattern>, library=<source if given>, limit=10, context=2). The tool returns the top files ranked by match density with two lines of context above and below each hit.
Read deeper context for the top 2-3 files. For each of the top files in the grep result (max 3), call read_doc(library=<lib>, path=<path>, line_start=<top-hit-line - 30>, line_end=<top-hit-line + 30>) to pull a ~60-line window. Skip this step if the user's pattern is very narrow (a literal symbol name) and the grep context already answers the question.
If grep returns nothing:
- If a source was specified, run list_indexed() to confirm the source is actually cached. If it isn't, suggest /web-add <source> and stop.
- If no library was specified, broaden the pattern once (e.g. add common prefixes/suffixes, drop word boundaries) and retry. If still nothing, surface the gap to the user.
If grep_docs says "search timed out": the pattern is likely catastrophic. Suggest a tighter pattern (no nested quantifiers, anchor with \b).

Output

Lead with the synthesized answer to the user's likely question, grounded in what you read.
Cite each source as source/path.md:line so the user can verify.
Don't dump the full grep output unless the user asked for it - the goal is an answer, not a search log.

Read the full file on GitHub · 45 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.

1mo ago First seen · 45 lines · 24 tokens per session scan A 8ce54b741ef0

Subscribe to this mod's changes

web-search is a command published in the GitHub repository raintree-technology/docpull (28 stars, last pushed 6d ago), licensed MIT. It adds 24 tokens to every session and 651 once invoked, about $0.0001 per session on Opus 5.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-30.

Python Research ai-training-data developer-tools documentation markdown web-scraping

batch

This page documents how the livewiki batch command is registered with the Commander CLI framework and how it formats batch run reports for human consumption.

eduardoabreu81/livewiki · 0 tokens

export

The livewiki export command turns the project's curated wiki into a deliverable artifact on disk: either a flattened snapshot under .livewiki/export/ / (for generic, github-wiki, and gitlab-wiki targets) or a synthesized repository-root README.md (for the readme target).

eduardoabreu81/livewiki · 0 tokens

web-search