A documentation search tool that looks through document text, titles, categories, and tags.

Use it to locate relevant guides, examples, or sections about a subject, with optional category or tag filters.

It removes the need to browse documentation files one by one when you are trying to find a topic or guide.

doc-search — Skill for Claude Code by esola-thomas

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.

Any agent

npx skills add esola-thomas/your-docs-mcp --skill doc-search

Clone the repo

git clone --depth 1 https://github.com/esola-thomas/your-docs-mcp

Made for: Claude Code.

Or install docs-mcp, the plugin that ships this one along with the rest of its 8 skills.

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/skills/esola-thomas/your-docs-mcp/doc-search/github.svg)](https://agentmods.dev/skills/esola-thomas/your-docs-mcp/doc-search)

Your own site

<a href="https://agentmods.dev/skills/esola-thomas/your-docs-mcp/doc-search"><img src="https://agentmods.dev/badge/skills/esola-thomas/your-docs-mcp/doc-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/skills/esola-thomas/your-docs-mcp/doc-search"><img src="https://agentmods.dev/badge/skills/esola-thomas/your-docs-mcp/doc-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 601 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.00035	$0.00601
Opus 5	$0.00017	$0.00300
Sonnet 5	$0.00007	$0.00120
Haiku 4.5	$0.00003	$0.00060

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

Security

Grade A, and why

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

docs-plugin/skills/doc-search/SKILL.md · 91 lines

How it starts

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

Search Documentation

Search across documentation files by content, metadata, or both.

Instructions

Parse the search query:
- $ARGUMENTS contains the search query and optional filters
- Extract: query text, --tag filters, --category filter
Search strategy:

Content Search

Use Grep to find matches in documentation content:

Search for: "$query"
In: docs/**/*.md, example/**/*.md

Metadata Search

For tag/category filters, read frontmatter from matching files:

If --tag specified: filter files where tags array contains the tag
If --category specified: filter files where category matches

Rank results by relevance:
- Title match: highest
- H2/H3 header match: high
- Content match: medium
- Tag match: medium
Present results:

## Search Results for "authentication"

### Exact Matches (3)

1. **Authentication Guide**
   `docs/guides/security/authentication.md`
   Category: Security | Tags: security, auth, api
   > "Learn how to implement authentication for the MCP server..."

2. **API Authentication**
   `example/api/authentication.md`
   Category: API | Tags: api, auth
   > "All API requests require authentication using..."

### Related (2)

3. **Getting Started**
   `docs/guides/getting-started.md`
   Category: Guides | Tags: beginner, setup
   > "...configure authentication in the setup process..."

---
Found 5 results in 0.2s

Filter	Usage	Example
`--tag`	Filter by tag	`--tag security`
`--category`	Filter by category	`--category API`
`--title`	Search titles only	`--title`

Example Queries

/doc-search authentication              # Find docs about auth
/doc-search --tag security              # All security-tagged docs
/doc-search config --category Guides    # Config docs in Guides
/doc-search "error handling" --tag api  # API error handling docs

Output Fields

For each result, show:

Title: From frontmatter
Path: Relative file path
Category: From frontmatter
Tags: From frontmatter
Snippet: Matching content with context (50 chars each side)

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

9d ago First seen · 91 lines · 35 tokens per session scan A 524d7e329cf4

Subscribe to this mod's changes

doc-search is a skill published in the GitHub repository esola-thomas/your-docs-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 601 once invoked, about $0.0002 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.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

doc-search