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 agentmods add skills/gxfn/wakeflow/wakeflow-controllernpx skills add GxFn/Wakeflow --skill wakeflow-controllergit clone --depth 1 https://github.com/GxFn/WakeflowWhat 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 | $0.00056 | $0.07481 |
| Opus 5 | $0.00028 | $0.03741 |
| Sonnet 5 | $0.00011 | $0.01496 |
| Haiku 4.5 | $0.00006 | $0.00748 |
Grade A, and why
wakeflow-controller 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 2d 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 — 600 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wakeflow Controller
Use this skill only from the controller window. CLAUDE.md owns hard judgment;
this skill owns the mechanical loop steps.
Purpose
Wakeflow Delivery Loop lets the controller fan out work to target window sessions, receive strict TargetResult records, inspect target-authored review inputs, run independent checks, and decide the next package. It does not replace planning, scope control, validation, or acceptance.
Direct-thread dispatch is the normal transport; on Claude Code a Wakeflow
thread id is the window's Claude Code session id, generated at launch and
stable across resumes. Every Wakeflow window (the controller included) is a
tmux-resident interactive claude session inside the workspace tmux server
session. In explicitly enabled unattended mode, keep reviewing results,
inspecting inputs, validating, deciding, planning next eligible packages, and
dispatching until final completion, a hard gate, explicit user stop, missing review inputs that need
human judgment, or no eligible TODO remains.
After an explicit v3 host-adapter outcome, record the exact transport and
readback fact through wakeflow_record_delivery operation=target-outcome.
Pending/unavailable pane visibility is sent-unconfirmed; it never authorizes
another pane read, resend, or lease release. The controller dispatch turn then
stops without claiming destination reachability. Do not keep the
turn open with sleep, repeated result review, repeated session reads, or
manual polling. The target returns later through one strict
wakeflow-target-result TargetResult and, if policy allows, a
controller-return delivery sent to the controller's own
tmux window. Status, review, and trace must derive from strict state, transport,
result, binding, and redacted host-projection facts. Silence is never
auto-judged: a long quiet spell may be a legitimate long tool call, so whether
a window is stalled remains the CONTROLLER'S judgment after an explicit
inspection. Do not arm per-dispatch watchers, poll panes, or use a synchronous
wait compatibility route.
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.
- 2d ago First seen · 600 lines · 56 tokens per session scan A 5f60577c9b85
wakeflow-controller is a skill published in the GitHub repository GxFn/Wakeflow (5 stars, last pushed 8d ago), licensed MIT. It adds 56 tokens to every session and 7,481 once invoked, about $0.0003 per session on Opus 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-31.
Other skills, from other repositories
fleet
Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave in isolated worktrees, collects discoveries, shares context between waves. Use when work decomposes into 3+ independent streams that can run simultaneously.
archon
Autonomous multi-session campaign agent. Decomposes large work into phases, delegates to sub-agents, reviews output, and maintains campaign state across context windows. Use for work that spans multiple sessions and needs persistent state, quality judgment, and strategic decomposition.
daemon
Continuous autonomous operation mode. Keeps campaigns running 24/7 by chaining Claude Code sessions via RemoteTrigger. Each session picks up from the campaign's continuation state, works until context runs low or the phase completes, then schedules the next session. Auto-stops on campaign completion or budget…
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
setup
First-run experience for the harness. Three modes: Recommended (guided, 3 min), Full Tour (guided + skill walkthrough, 8 min), and Express (zero questions, 30 sec). Installs hooks first, detects stack, configures harness.json, runs a live demo on real code, and prints a reference card.
dashboard
Real-time harness observability dashboard. Reads campaigns, fleet sessions, telemetry, and pending queues to present a snapshot of harness state at a glance. Invoked by /dashboard, /do status, or phrases like "what's happening" and "show activity".