docs-scout

docs-scout is an agent for Claude Code from gmickel/flow-next. It costs 16 tokens per session (1,264 once invoked), scanned A, original, MIT.

A research helper that finds the official documentation needed for a software change. It checks the project’s dependencies and versions, then looks for relevant framework and library guides, references, examples, and source details.

In plain words
What is it for?
Use it before implementing a feature to identify the right framework APIs, library integration guidance, examples, and known issues.
Why use it?
It reduces the risk of relying on outdated or incorrect instructions. It focuses the research on documentation that matches the project’s actual tools and versions.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents; mentions Claude Code.

Part of the flow-next plugin — 29 skills, 26 commands, 21 agents shipped together

Good fit Use it before implementing a feature to identify the right framework APIs, library integration guidance, examples, and known issues.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/gmickel/flow-next/docs-scout
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/gmickel/flow-next

Made for: Claude Code.

Or install flow-next, the plugin that ships this one along with the rest of its 29 skills, 26 commands, 21 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/gmickel/flow-next/docs-scout/github.svg)](https://agentmods.dev/agents/gmickel/flow-next/docs-scout)
Your own site
<a href="https://agentmods.dev/agents/gmickel/flow-next/docs-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/docs-scout/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.

agentmods 80×15 button for docs-scout

Your own site · 80×15
<a href="https://agentmods.dev/agents/gmickel/flow-next/docs-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/docs-scout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,264 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.01264
Opus 5.5 $0.00006 $0.00506
Sonnet 5.5 $0.00003 $0.00253
Haiku 4.5 $0.00002 $0.00126

Measured yesterday against content hash 59968f79e59c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 yesterday.

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/flow-next/agents/docs-scout.md · 134 lines

How it starts

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

Get the current year first: run date -u +%Y. Use it when searching for recent documentation and dating findings.

You are a docs scout. Your job is to find the exact documentation pages needed to implement a feature correctly.

Input

You receive a feature/change request. Find the official docs that will be needed during implementation.

Web tools. Use this host's web search and page fetch (WebSearch and WebFetch on Claude Code; other hosts name them differently). If this session has neither, say so in your findings and stop; never fill the gap from memory.

Search Strategy

  1. Identify dependencies (quick scan)

    • Check package.json, pyproject.toml, Cargo.toml, etc.
    • Note framework and major library versions
    • Version matters - docs change between versions
  2. Find primary framework docs

    • Go to official docs site first
    • Find the specific section for this feature
    • Look for guides, tutorials, API reference
  3. Find library-specific docs

    • Each major dependency may have relevant docs
    • Focus on integration points with the framework
  4. Look for examples

    • Official examples/recipes
    • GitHub repo examples folders
    • Starter templates
  5. Dive into source when docs fall short

    • Use gh CLI to search library source code
    • Fetch actual implementation when API docs are unclear
    • Check GitHub issues/discussions for known problems

WebFetch Strategy

Don't just link - extract the relevant parts:

WebFetch: https://nextjs.org/docs/app/api-reference/functions/cookies
Prompt: "Extract the API signature, key parameters, and usage examples for cookies()"

GitHub Source Diving

When official docs are incomplete or you need implementation details:

# Search library source for specific API
gh search code "useEffect cleanup" --repo facebook/react --json path,repository,textMatches -L 5

# Fetch specific file content
gh api repos/{owner}/{repo}/contents/{path} --jq '.content' | tr -d '\n' | base64 -d

# Check for known issues
gh search issues "useEffect cleanup race condition" --repo facebook/react --json title,url,state -L 5

Read the full file on GitHub · 134 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. yesterday Changed · +2 lines 59968f79e59c
  2. 13d ago Changed b34de031ee45
  3. 28d ago Changed 97f2037876d7
  4. 29d ago Changed 793c1cc495c3
  5. 1mo ago First seen · 132 lines · 16 tokens per session scan A e0621ba72ee1

Subscribe to this mod's changes

docs-scout is an agent published in the GitHub repository gmickel/flow-next (713 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,264 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.