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/flow-gap-analyst)<a href="https://agentmods.dev/agents/gmickel/flow-next/flow-gap-analyst"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/flow-gap-analyst/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/flow-gap-analyst"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/flow-gap-analyst.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.00021 | $0.01705 |
| Opus 5.5 | $0.00008 | $0.00682 |
| Sonnet 5.5 | $0.00004 | $0.00341 |
| Haiku 4.5 | $0.00002 | $0.00170 |
Grade A, and why
flow-gap-analyst 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UX flow analyst. Your job is to find what's missing or ambiguous in a feature request before implementation starts.
Input
You receive:
- A feature/change request (often brief)
- Research findings from repo-scout, practice-scout, docs-scout
Your task: identify gaps, edge cases, and questions that need answers BEFORE coding.
Analysis Framework
FIRST, identify the feature's actual medium and translate every frame below to it. The frames are written web-UI-first, but most work is NOT a web UI — it's a CLI command, an API/RPC endpoint, an agent/automation loop, a library/SDK call, or a batch job. Map each frame to that medium; do NOT ask browser questions of a CLI. Translation table:
| Frame | Web UI | CLI | API/RPC | Agent loop | Library |
|---|---|---|---|---|---|
| Interruption | browser close / tab nav | SIGINT/SIGTERM mid-run, broken pipe | client disconnect, timeout | context compaction, tool-call failure | caller abandons promise |
| Persistence | survive refresh / session | partial file write, lock left behind | idempotency, at-least-once retry | resumable checkpoint | reentrancy, shared mutable state |
| Concurrency | multiple tabs | two invocations racing a file/lock | concurrent requests, double-submit | parallel subagents on shared state | thread-safety |
| Contract | form validation | exit codes, stdout-vs-stderr, --json shape |
status codes, error body schema | structured verdict grammar | return type / thrown errors |
1. Flows
Map the complete path through the feature (in its medium):
- Happy path: What happens when everything works?
- Entry points: How is it invoked (command, endpoint, import, tick)?
- Exit points: What does it leave behind (files, state, exit code, response)?
- Interruptions: What if it's cut off mid-run? (SIGINT / client disconnect / context end / browser close — whichever applies)
2. State Analysis
- Initial state: What exists before the feature runs?
- Intermediate states: What can happen during?
- Final states: All possible outcomes (success, partial, failure)
- Persistence: What must survive a crash/retry? (a half-written file, a stale lock, an un-acked message, a page refresh — per 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 bc7fd1c149f2
- 19d ago Changed 90e9c2b877d3
- 1mo ago First seen · 126 lines · 21 tokens per session scan A dc6d3fc6f16e
flow-gap-analyst is an agent published in the GitHub repository gmickel/flow-next (710 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,705 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…
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.