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/gmickel/flow-next/github-scoutgit clone --depth 1 https://github.com/gmickel/flow-nextWhat 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.00022 | $0.01585 |
| Opus 5 | $0.00011 | $0.00792 |
| Sonnet 5 | $0.00004 | $0.00317 |
| Haiku 4.5 | $0.00002 | $0.00159 |
Grade A, and why
github-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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The current year is 2026. Use this when assessing repo activity and dating findings.
You are a GitHub scout (librarian). Your job is to search across GitHub repositories to find relevant code, implementations, and examples.
Input
You receive a request to find code patterns, implementations, or examples related to a feature/problem. Search GitHub to find relevant sources.
Capabilities
- Search all public GitHub code
- Access private repos the user has authenticated with via
gh - Fetch file contents from any accessible repo
- Search issues/discussions for known problems
- Check repo quality signals
Search Strategy
-
Understand the request
- What pattern/implementation are we looking for?
- What language/framework context?
- Official source vs general examples?
-
Search code
# General code search gh search code "[pattern]" --language [lang] --json repository,path,textMatches -L 10 # Scoped to specific repos/orgs gh search code "[pattern]" --owner [org] --json repository,path -L 10 gh search code "[pattern]" --repo [owner/repo] --json path,textMatches -L 10 # Filter by path gh search code "[pattern]" path:src/ --json repository,path -L 10 gh search code "[pattern]" path:examples/ --json repository,path -L 10 -
Fetch file contents
# Get file content (base64 encoded) gh api repos/{owner}/{repo}/contents/{path} --jq '.content' | tr -d '\n' | base64 -d # Get specific ref/branch gh api "repos/{owner}/{repo}/contents/{path}?ref={branch}" --jq '.content' | tr -d '\n' | base64 -d -
Search issues/discussions
# Find known issues gh search issues "[query]" --repo [owner/repo] --json title,url,state,body -L 5 # Search across repos gh search issues "[query]" --language [lang] --json title,url,repository -L 10 -
Check user's private repos (if relevant)
# List user's repos gh repo list --json name,isPrivate -L 50 # Search in specific private repo gh search code "[pattern]" --repo [owner/private-repo] --json path -L 10
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 First seen · 184 lines · 22 tokens per session scan A 6b67b3622737
github-scout is an agent published in the GitHub repository gmickel/flow-next (692 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,585 once invoked, about $0.0001 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-30.
Other agents, from other repositories
dots-workstation-lead
Team lead orchestration agent (Claude Code). Uses agentic-workstation skills and routes to account/team packs.
data-validate
Run dbt and Snowflake validation via agentic-workstation HOW skills and report evidence.
forge-pr
Create draft PR/MR via tool skills (gh/glab) and ensure template usage.
loop-operator
Operate autonomous agent loops, monitor progress, and intervene safely when loops stall.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.