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 skills add gmickel/flow-next --skill flow-next-flowgit 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/skills/gmickel/flow-next/flow-next-flow)<a href="https://agentmods.dev/skills/gmickel/flow-next/flow-next-flow"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-flow/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/skills/gmickel/flow-next/flow-next-flow"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-flow.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.00053 | $0.02517 |
| Opus 5.5 | $0.00021 | $0.01007 |
| Sonnet 5.5 | $0.00011 | $0.00503 |
| Haiku 4.5 | $0.00005 | $0.00252 |
Grade A, and why
flow-next-flow 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 11d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/flow-next:flow - the conductor
Flow chooses the next step so the user does not have to. It reads what it was given, routes from the shared routing reference, runs the routed stage skill, and continues until the next decision that belongs to a human. It re-implements no stage logic: capture, refine, plan, plan-review, work, qa, make-pr, resolve-pr, and land keep their own contracts, receipts, and gates.
Role: conductor, inline (no context: fork) so plain-text numbered prompt stays reachable. On hosts without it, fall back to a plain-text numbered prompt with a final Other - type your own answer option.
The hop loop is Steps 1 to 5 below. Read a reference only at the step that names it.
Preamble
CRITICAL: flowctl is BUNDLED - NOT installed globally. which flowctl will fail (expected). Define once; subsequent blocks (here and in the steps below) use $FLOWCTL:
FLOWCTL="${CODEX_HOME:-$HOME/.codex}/scripts/flowctl"
[ -x "$FLOWCTL" ] || FLOWCTL="<plugin-root>/scripts/flowctl" # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
[ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl"
Mode detection
Parse $ARGUMENTS as exact tokens (never substrings), before any read or write: --auto sets AUTO=1, and so does --goal, because goal mode is unattended; --tick sets AUTO_TICK=1 (one hop, then stop; meaningful only with --auto or --goal); --explain sets EXPLAIN=1; --review=<backend> sets REVIEW_OVERRIDE and is passed through unchanged to every stage it dispatches. The destination parse is shared by both modes:
FLOW_UNTIL=""
FLOW_DESTINATION_ERROR=0
LAND_AUTHORIZED=0
LAND_SCOPE_SPEC=""
LAND_SCOPE_PR=""
AUTO=0
for ARG in $ARGUMENTS; do
case "$ARG" in
--auto|--goal) AUTO=1 ;;
--until=merge) FLOW_UNTIL=merge ;;
--until|--until=*) FLOW_DESTINATION_ERROR=1 ;;
esac
done
if [ "$FLOW_DESTINATION_ERROR" = 1 ]; then
if [ "$AUTO" = 1 ]; then
echo 'PILOT_VERDICT=NEEDS_HUMAN spec=- stage=- reason="invalid destination; use --until=merge"'
else
echo 'NEEDS_HUMAN: invalid destination; use --until=merge'
fi
exit 1
fi
export FLOW_UNTIL
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 313 B
- auto.md 50 KB
- references/backlog-mode.md 44 KB
- references/defect-intake.md 2.8 KB
- references/diagnose-artifact.md 2.0 KB
- references/explain.md 840 B
- references/gate-selection-more.md 1.9 KB
- references/gate-selection.md 1.7 KB
- references/goal-mode.md 14 KB
- references/measure-behaviour-change.md 2.1 KB
- references/no-argument.md 1.5 KB
- references/plan-vs-no-plan.md 2.6 KB
- references/prototype-before-ask.md 3.9 KB
- references/prove-diff-safety.md 2.1 KB
- references/qa-auto.md 1.1 KB
- references/qa-stage.md 3.0 KB
- references/route-matrix-more.md 4.8 KB
- references/route-matrix.md 9.6 KB
- references/spec-count.md 1.6 KB
- references/tail.md 6.6 KB
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.
- 11d ago Changed 2bc392f2d106
- 12d ago Changed · +1 tokens per session 220c8ae620ad
- 18d ago Changed · +76 lines 127c54b1549a
- 24d ago Changed c78ae4e8f594
- 26d ago Changed · -9 lines d9679584da7c
- 1mo ago Changed · -1 lines 8a1e0439e326
- 1mo ago Changed · +30 lines · +1 tokens per session 24dd84b8cccb
- 1mo ago First seen · 66 lines · 51 tokens per session scan A e7a3de54012f
flow-next-flow is a skill published in the GitHub repository gmickel/flow-next (713 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 2,517 once invoked, about $0.0002 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-09-12.
Other skills, from other repositories
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
project-execution
Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.
st-setup-project
Smalltalk (Pharo/Squeak) project boilerplate creator. Use when the user asks to create a new Pharo/Smalltalk project from scratch, when project structure is missing (no src/ directory or .project file), when the user wants to start a new Smalltalk development project, or when setting up BaselineOf, Core, and Tests…
kanban
Use when a prompt contains a new bug/feature/change not yet tracked, or when an item's status changes — capture and maintain it in the project's beads tracker (Inbox→Backlog with Definition of Ready, priorities, the pipe-separated note format).
project-discuss
A project-discussion management workflow that keeps track of decisions, open questions, project context, and incidents. It uses a project's cadence files, which are shared records for ongoing discussions and decisions.
subtask-update
Update subtask with fixes or new steps. Two trigger modes: (A) Auto-called by autoworker:gate-check on FAIL — reads FAIL info, adds supplementary steps. (B) User calls with a finding/bug during testing — diagnoses, fixes, updates subtask. Both modes end by invoking autoworker:dispatch to re-enter the loop.