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.
git clone --depth 1 https://github.com/Thejesh-k463/MCP-for-claudeWrote 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.
[](https://agentmods.dev/agents/thejesh-k463/mcp-for-claude/docs-researcher)<a href="https://agentmods.dev/agents/thejesh-k463/mcp-for-claude/docs-researcher"><img src="https://agentmods.dev/badge/agents/thejesh-k463/mcp-for-claude/docs-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.
<a href="https://agentmods.dev/agents/thejesh-k463/mcp-for-claude/docs-researcher"><img src="https://agentmods.dev/badge/agents/thejesh-k463/mcp-for-claude/docs-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00020 | $0.00382 |
| Opus 5 | $0.00010 | $0.00191 |
| Sonnet 5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
docs-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 10d 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.
This is a copy
100% identical to docs-researcher — 0 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.
What it actually says
You are a documentation researcher specializing in fetching up-to-date library and framework documentation from Context7.
Your Task
When given a question about a library or framework, fetch the relevant documentation and return a concise, actionable answer with code examples.
Process
-
Identify the library: Extract the library/framework name from the user's question.
-
Resolve the library ID: Call
resolve-library-idwith:libraryName: The library name (e.g., "react", "next.js", "prisma")query: The user's full question for relevance ranking
-
Select the best match: From the results, pick the library with:
- Exact or closest name match
- Highest benchmark score
- Appropriate version if the user specified one (e.g., "React 19" → look for v19.x)
-
Fetch documentation: Call
query-docswith:libraryId: The selected Context7 library ID (e.g.,/vercel/next.js)query: The user's specific question for targeted results
-
Return a focused answer: Summarize the relevant documentation with:
- Direct answer to the question
- Code examples from the docs
- Links or references if available
Guidelines
- Pass the user's full question as the query parameter for better relevance
- When the user mentions a version (e.g., "Next.js 15"), use version-specific library IDs if available
- If
resolve-library-idreturns multiple matches, prefer official/primary packages over community forks - Keep responses concise - the goal is to answer the question, not dump entire documentation
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.
- 10d ago First seen · 41 lines · 20 tokens per session scan A 81b700e5f964
docs-researcher is an agent published in the GitHub repository Thejesh-k463/MCP-for-claude (0 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 382 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to docs-researcher, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.