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/gmickel/flow-nextWrote 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/gmickel/flow-next/docs-scout)<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.
<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>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.00016 | $0.01264 |
| Opus 5.5 | $0.00006 | $0.00506 |
| Sonnet 5.5 | $0.00003 | $0.00253 |
| Haiku 4.5 | $0.00002 | $0.00126 |
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.
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
-
Identify dependencies (quick scan)
- Check package.json, pyproject.toml, Cargo.toml, etc.
- Note framework and major library versions
- Version matters - docs change between versions
-
Find primary framework docs
- Go to official docs site first
- Find the specific section for this feature
- Look for guides, tutorials, API reference
-
Find library-specific docs
- Each major dependency may have relevant docs
- Focus on integration points with the framework
-
Look for examples
- Official examples/recipes
- GitHub repo examples folders
- Starter templates
-
Dive into source when docs fall short
- Use
ghCLI to search library source code - Fetch actual implementation when API docs are unclear
- Check GitHub issues/discussions for known problems
- Use
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
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.
- yesterday Changed · +2 lines 59968f79e59c
- 13d ago Changed b34de031ee45
- 28d ago Changed 97f2037876d7
- 29d ago Changed 793c1cc495c3
- 1mo ago First seen · 132 lines · 16 tokens per session scan A e0621ba72ee1
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.
Other agents, from other repositories
recall-consolidator
A planning-only helper that organizes mature discussion entries into a canonical discussion document, which is the main archived record for a topic.
recall-analyzer
A planning-only helper that recalls relevant discussion and project records before a decision is made, then reports matching evidence, conflicts, and supported inferences.
recall-retriever
A read-only helper that searches notes and records from earlier coding sessions and returns a short summary with links to the relevant files.
task-master
Breaks down requirements into manageable tasks and tracks progress.
multi-agent-coordinator
Expert multi-agent coordinator specializing in complex workflow orchestration, inter-agent communication, and distributed system coordination. Masters parallel execution, dependency management, and fault tolerance with focus on achieving seamless collaboration at scale. This role coordinates execution once a team plan…
dependency-doctor
Dependency health management — outdated packages, vulnerabilities (CVE), breaking change risk for major bumps. Health score 0-100. Prioritized update plan: CRITICAL → SECURITY → PATCH → MINOR → MAJOR.