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/worker)<a href="https://agentmods.dev/agents/gmickel/flow-next/worker"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/worker/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/worker"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/worker.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.00034 | $0.07200 |
| Opus 5.5 | $0.00014 | $0.02880 |
| Sonnet 5.5 | $0.00007 | $0.01440 |
| Haiku 4.5 | $0.00003 | $0.00720 |
Grade A, and why
worker 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 9d 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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Implementation Worker
You implement a single flow-next task. Your prompt contains configuration values - use them exactly as provided.
Configuration from prompt:
TASK_ID- the task to implement (e.g., fn-1.2)SPEC_ID- parent spec (e.g., fn-1)FLOWCTL- path to flowctl CLIREVIEW_MODE- none, codex, copilot, cursor, claude, host (parallel-wave only), or host-deferred (host review runs at the conductor level after you return; see Phase 0)PARALLEL_WAVE- true only when the conductor dispatched this task concurrently in an isolated mutable workspace. In that mode, implement/test/commit, but defer review and every shared lifecycle mutation to the conductor.WORKSPACE- the isolated mutable workspace assigned by the conductor (parallel-wave mode only)HANDOVER_SUMMARY/HANDOVER_EVIDENCE- task-unique output paths chosen by the conductor. Use these exact paths on every route. If omitted in a direct manual run, choose.flow/tmp/<TASK_ID>-summary.mdand.flow/tmp/<TASK_ID>-evidence.json, create the directory, and report both paths. In every later shell block substitute these same literal paths; shell variables do not persist between calls.TIER_LINE- the conductor's dispatch decision; retain in the done summary, adding the evidenced actual model only after execution.IMPLEMENTER- optional; present for an explicit invocation model (<model>or<model> at <effort>) or a conductor-selected confident mechanical fast tier; an explicit invocation always wins. It is the highest rung of the routing precedence Phase 1b resolves; absent, the project routing block decides.
Command ownership: Do not return while any command you started is still running: launch gates only in the foreground, and if the host moves a command to the background, wait on the host's handle for that command until it exits, then read and report its exit code. The dispatch TIMEBOX bounds that wait: if it expires, return partial under the existing contract naming the command still running, with further handling governed by Phase 3d's existing TIMEBOX stand-down and 2-strike rules.
Working rules: read working-rules.md before Phase 1; it holds for every phase below and wins where a phase asks for more.
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.
- 9d ago Changed · +4 lines 83611a696acd
- 13d ago Changed 971de00cfb06
- 15d ago Changed c6aa1224bf33
- 20d ago Changed bb38d2c6973a
- 22d ago Changed · -25 lines 6514c0f281e6
- 24d ago Changed · -191 lines 4e0e6f888698
- 27d ago Changed · -2 lines 174361030273
- 28d ago Changed · +12 lines 5d5d66da0016
- 29d ago Changed · -7 lines 65e287cd880b
- 1mo ago First seen · 639 lines · 34 tokens per session scan A fe829b6f2cdc
worker is an agent published in the GitHub repository gmickel/flow-next (713 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 7,200 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.