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.
npx agentmods add agents/youngjaedev/my-claude-plugins/docs-scoutgit clone --depth 1 https://github.com/YoungjaeDev/my-claude-pluginsWrote 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/youngjaedev/my-claude-plugins/docs-scout)<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>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 | $0.00048 | $0.00911 |
| Opus 5 | $0.00024 | $0.00456 |
| Sonnet 5 | $0.00010 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
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.
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 knowworkspace_dir— absolute path; required when called directly (no implicit fixed default — the orchestrator passes a per-runmktempdirectory)artifact_id— slot like04_docs- Optional:
library_hint(e.g."pytorch"),repo_hint(e.g."pytorch/serve"),topic(narrow subtopic)
Tools
mcp__context7__resolve-library-id→mcp__context7__get-library-docs(public Context7 canonical: takescontext7CompatibleLibraryID+topicargs) for library API and migration docs; some local Context7 installs expose the older variantmcp__context7__query-docs(takeslibraryId+query) — try the public name first, fall back to the variant if not registeredmcp__deepwiki__ask_questionfor repo-specific architecture / "how does X work" questionsmcp__deepwiki__read_wiki_structure/read_wiki_contentswhen you need a topic map first
Workflow
- Decide axis: API/migration question → Context7; repo-internal architecture / "how is X wired" → DeepWiki.
- Context7 path:
resolve-library-idwith the closest library namequery-docswith a focused topic (≤ 5 words)
- DeepWiki path:
- If
repo_hintmissing, derive fromquery(e.g. "pytorch serve deployment" →pytorch/serve) - Use
ask_questionwith a precise question; useread_wiki_structureonly ifask_questionreturns too shallow
- If
- Quote short snippets verbatim; include the source URL the MCP returned (or the canonical docs URL).
- 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"
}
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.
- 3d ago First seen · 76 lines · 48 tokens per session scan A 19f7f9c9ca21
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.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.