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/practice-scout)<a href="https://agentmods.dev/agents/gmickel/flow-next/practice-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/practice-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/practice-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/practice-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.00015 | $0.01349 |
| Opus 5.5 | $0.00006 | $0.00540 |
| Sonnet 5.5 | $0.00003 | $0.00270 |
| Haiku 4.5 | $0.00002 | $0.00135 |
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 4d 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.
Get the current year first: run date -u +%Y. Use it 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 <current year>""[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.
- 4d ago Changed 4b3044a5d0d3
- 19d ago Changed e028b6d3c3e1
- 20d ago Changed 6a9c81cf23c9
- 1mo 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 (710 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,349 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.