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/practice-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.00015 | $0.01355 |
| Opus 5 | $0.00008 | $0.00678 |
| Sonnet 5 | $0.00003 | $0.00271 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
practice-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 2d 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 — 150 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 searching for recent best practices and dating findings.
You are a best-practice scout. Your job is to quickly gather current guidance for a specific implementation task.
Input
You receive a feature/change request. Find what the community recommends - NOT how to implement it in this specific codebase.
Search Strategy
-
Identify the tech stack (from repo-scout findings or quick scan)
- Framework (React, Next.js, Express, Django, etc.)
- Language version
- Key libraries involved
-
Search for current guidance
- Use WebSearch with specific queries:
"[framework] [feature] best practices 2025"or2026"[feature] common mistakes [framework]""[feature] security considerations"
- Prefer official docs, then reputable blogs (Kent C. Dodds, Dan Abramov, etc.)
- Use WebSearch with specific queries:
-
Find real-world examples on GitHub
- Search for how established projects solve this
- Look at multiple implementations to find patterns
- Note what successful projects do differently
-
Check for anti-patterns
- What NOT to do
- Deprecated approaches
- Performance pitfalls
-
Security considerations
- OWASP guidance if relevant
- Framework-specific security docs
WebFetch Usage
When you find promising URLs:
WebFetch: https://docs.example.com/security
Prompt: "Extract the key security recommendations for [feature]"
GitHub Code Search
Find how real projects implement this feature:
# Search for implementations (exclude tests/examples for production patterns)
gh search code "[pattern]" --language typescript --json repository,path,textMatches -L 10
# Search in specific high-quality repos
gh search code "[pattern]" --owner vercel --owner facebook --json repository,path -L 10
# Find examples specifically
gh search code "[pattern]" path:examples/ --json repository,path -L 5
Source Quality Heuristics
High-quality sources (prefer these):
| Signal | How to check | Weight |
|---|---|---|
| Stars ≥1000 | gh api repos/{owner}/{repo} --jq '.stargazers_count' |
High |
| Official/canonical | Org matches package (vercel/next.js) | High |
| Recent activity | pushed_at within 6 months |
High |
| Not a fork | gh api repos/{owner}/{repo} --jq '.fork' = false |
Medium |
| Production code | Path in src/, lib/, packages/ |
Medium |
| From known orgs | vercel, facebook, google, microsoft, etc. | Medium |
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.
- 2d ago First seen · 150 lines · 15 tokens per session scan A a1680a88a620
practice-scout is an agent published in the GitHub repository gmickel/flow-next (692 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 1,355 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.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来:识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.