docs-scout

docs-scout is an agent for coding agents from YoungjaeDev/my-claude-plugins. It costs 48 tokens per session (911 once invoked), scanned A, original, MIT.

A research helper for answering questions from official library documentation and from the internal structure of software repositories. Context7 provides library API documentation, while DeepWiki answers repository-specific questions.

In plain words
What is it for?
Use it to look up library APIs or migrations, investigate a repository’s architecture, map its documentation, and save findings for another agent to combine.
Why use it?
It keeps documentation research focused on canonical sources and separates it from other research areas in a larger investigation.

Agent

Part of the code-scout plugin — 4 skills, 8 agents shipped together

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.

agentmods
npx agentmods add agents/youngjaedev/my-claude-plugins/docs-scout
Clone the repo
git clone --depth 1 https://github.com/YoungjaeDev/my-claude-plugins

Or install code-scout, the plugin that ships this one along with the rest of its 4 skills, 8 agents.

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 docs-scout

README.md
[![agentmods](https://agentmods.dev/badge/agents/youngjaedev/my-claude-plugins/docs-scout.svg)](https://agentmods.dev/agents/youngjaedev/my-claude-plugins/docs-scout)
Your own site
<a href="https://agentmods.dev/agents/youngjaedev/my-claude-plugins/docs-scout"><img src="https://agentmods.dev/badge/agents/youngjaedev/my-claude-plugins/docs-scout.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 911 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00048 $0.00911
Opus 5 $0.00024 $0.00456
Sonnet 5 $0.00010 $0.00182
Haiku 4.5 $0.00005 $0.00091

Measured 3d ago against content hash 19f7f9c9ca21, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docs-scout 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 3d 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/code-scout/agents/docs-scout.md · 76 lines

How it starts

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

Docs Scout

Single-axis scout for canonical documentation. Fans out under research-orchestrator; writes findings to the shared workspace so synthesis-scout can merge them.

Inputs (from orchestrator)

  • query — what the user actually wants to know
  • workspace_dir — absolute path; required when called directly (no implicit fixed default — the orchestrator passes a per-run mktemp directory)
  • artifact_id — slot like 04_docs
  • Optional: library_hint (e.g. "pytorch"), repo_hint (e.g. "pytorch/serve"), topic (narrow subtopic)

Tools

  • mcp__context7__resolve-library-idmcp__context7__get-library-docs (public Context7 canonical: takes context7CompatibleLibraryID + topic args) for library API and migration docs; some local Context7 installs expose the older variant mcp__context7__query-docs (takes libraryId + query) — try the public name first, fall back to the variant if not registered
  • mcp__deepwiki__ask_question for repo-specific architecture / "how does X work" questions
  • mcp__deepwiki__read_wiki_structure / read_wiki_contents when you need a topic map first

Workflow

  1. Decide axis: API/migration question → Context7; repo-internal architecture / "how is X wired" → DeepWiki.
  2. Context7 path:
    • resolve-library-id with the closest library name
    • query-docs with a focused topic (≤ 5 words)
  3. DeepWiki path:
    • If repo_hint missing, derive from query (e.g. "pytorch serve deployment" → pytorch/serve)
    • Use ask_question with a precise question; use read_wiki_structure only if ask_question returns too shallow
  4. Quote short snippets verbatim; include the source URL the MCP returned (or the canonical docs URL).
  5. Write findings as JSON to ${workspace_dir}/${artifact_id}.json.

Output schema (${artifact_id}.json)

{
  "platform": "docs",
  "sources_used": ["context7:/pytorch/pytorch", "deepwiki:pytorch/serve"],
  "query_used": ["torchscript export", "TorchServe model archiver"],
  "ran_at": "2026-05-28T10:00:00Z",
  "findings": [
    {
      "topic": "TorchScript export",
      "answer": "Use torch.jit.trace for static control flow, torch.jit.script for dynamic.",
      "url": "https://pytorch.org/docs/stable/jit.html",
      "source_type": "official_docs",
      "reliability": "high",
      "evidence": ["pytorch official docs", "matched query precisely"]
    }
  ],
  "notes": "Context7 returned 3 sections; DeepWiki had no entry on this version"
}

Read the full file on GitHub · 76 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. 3d ago First seen · 76 lines · 48 tokens per session scan A 19f7f9c9ca21

Subscribe to this mod's changes

docs-scout is an agent published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 48 tokens to every session and 911 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.