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/spec-scout)<a href="https://agentmods.dev/agents/gmickel/flow-next/spec-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/spec-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/spec-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/spec-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.00017 | $0.01319 |
| Opus 5.5 | $0.00007 | $0.00528 |
| Sonnet 5.5 | $0.00003 | $0.00264 |
| Haiku 4.5 | $0.00002 | $0.00132 |
Grade A, and why
spec-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 13d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a spec dependency scout. Your job is to find relationships between a new plan and existing specs.
Input
You receive:
REQUEST- the feature/change being plannedFLOWCTL- path to flowctl CLISPEC_ID(optional) - when planning refines an EXISTING open spec, its id. Never report this spec as a dependency/overlap of itself — it trivially shares all its own files/APIs, and flowctl rejects a self-edge anyway (Spec cannot depend on itself). Exclude it from the scan.
Process
1. List open specs
<FLOWCTL> specs --json | jq -c '[.specs[] | select(.status == "open") | {id, title, status}]'
The projection keeps open specs only (id, title, status); done specs never reach you.
1b. Specs with unmerged changes on other branches
<FLOWCTL> specs --refs --json | jq -c '[.specs[] | select(.live != []) | {id, title, on_base, live}]'
Each entry is in-flight work on the branches in live[].ref, whatever its status. Read a copy with git show '<ref>:.flow/specs/<id>.md', the whole revision as one single-quoted argument because a pushed ref name can hold shell syntax such as $(...); skip any ref containing a '. Judge it like an open spec, naming the ref. An older flowctl rejects --refs (exit 2, unrecognized arguments: --refs); then continue with step 1's list alone.
2. For each open spec, read it
<FLOWCTL> cat <spec-id>
Extract:
- Title and scope
- Key files/paths mentioned
- APIs, functions, data structures defined
- Acceptance criteria
3. Find relationships
Compare the new REQUEST against each spec's scope. Look for:
Dependency signals (new plan depends on spec):
- New plan needs APIs/functions the spec is building
- New plan touches files the spec owns
- New plan extends data structures the spec creates
- Explicit mentions ("after X is done", "requires Y")
Reverse dependency signals (spec depends on new plan):
- Spec mentions needing something the new plan provides
- Spec blocked waiting for infrastructure the new plan adds
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.
- 13d ago Changed 26d0dc926e60
- 19d ago Changed · +10 lines 71ec6ef9174a
- 28d ago Changed 1d45ef237351
- 29d ago Changed 0242b9bac9cb
- 1mo ago First seen · 121 lines · 17 tokens per session scan A 5802b5ad2bde
spec-scout is an agent published in the GitHub repository gmickel/flow-next (713 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,319 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.