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/GxFn/WakeflowWrote 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/commands/gxfn/wakeflow/next)<a href="https://agentmods.dev/commands/gxfn/wakeflow/next"><img src="https://agentmods.dev/badge/commands/gxfn/wakeflow/next/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/commands/gxfn/wakeflow/next"><img src="https://agentmods.dev/badge/commands/gxfn/wakeflow/next.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.00016 | $0.00199 |
| Opus 5.5 | $0.00006 | $0.00080 |
| Sonnet 5.5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
next 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 20d 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.
What it actually says
Take the next step on the active Demand.
Load the wakeflow-controller skill and follow the "Main flow" section for
whichever step the workspace names; the planning, delivery and review depth is
in its references/delivery-and-review.md.
First tool call: wakeflow_status, passing a Demand id if the user named one.
Its next actions are the authority on what comes next - do not infer the step
from the conversation.
Then do that one step, and stop. Do not run ahead into the step after it: each step produces state that the next one has to read.
Report what you did, the evidence Wakeflow recorded for it, and what is now next. If the next step belongs to the Design window or to a target window, say so instead of doing it here.
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.
- 20d ago First seen · 22 lines · 16 tokens per session scan A 6e5a9d6bfcde
next is a command published in the GitHub repository GxFn/Wakeflow (5 stars, last pushed 9d ago), licensed MIT. It adds 16 tokens to every session and 199 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-09-26.
Other commands, from other repositories
start-development
Start development workflow process in Moira.
retro
"What actually happened? What moved, what stuck, what am I avoiding?".
abort
Read .claude/RUNTIME.md and .claude/policies/advisory.md first. Then read .claude/command-guides/playbook-commands.md and execute only /abort with the user's arguments: $ARGUMENTS.
release-flow
Portable gated release flow — deterministic gate + vendor-agnostic independent reviewer, runnable from any harness.
sdlc
Master orchestrator for the complete 5-phase SDLC pipeline. Runs all phases sequentially with approval gates and handoffs between each phase. Organizes artifacts into handoffs/, docs/, and projects/ directories.
to-issues
Create one Linear issue per slice from an existing scope.json. Run standalone to (re)create issues without rerunning the full Plan phase. Falls back to docs/issues.md if Linear MCP is unavailable.