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/pod)<a href="https://agentmods.dev/commands/gxfn/wakeflow/pod"><img src="https://agentmods.dev/badge/commands/gxfn/wakeflow/pod/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/pod"><img src="https://agentmods.dev/badge/commands/gxfn/wakeflow/pod.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.00020 | $0.00235 |
| Opus 5.5 | $0.00008 | $0.00094 |
| Sonnet 5.5 | $0.00004 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
pod 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
Create or close a Wakeflow pod.
Load the wakeflow-controller skill and follow its "Step 13 - Close the pod"
section; the full create and close procedure is in its
references/workspace-and-windows.md.
First tool call: wakeflow_pod in preview, for the create or close intent the
user asked for. Preview writes nothing; show the user the plan before applying
it with exactly what preview returned.
On create: one config transaction registers the pod's window set and one worktree intent per repository. Creating the worktrees and launching the windows are your host actions, and each window must then be registered.
On close: the pod's Demand must already be archived and the user must have merged or abandoned its branch. Record the branch dispositions truthfully - never record a branch as merged that you have not seen merged - then retire the windows, remove the checkouts, and remove the pod in that order.
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 · 24 lines · 20 tokens per session scan A 1aec90e5b1ed
pod is a command published in the GitHub repository GxFn/Wakeflow (5 stars, last pushed 9d ago), licensed MIT. It adds 20 tokens to every session and 235 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
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
standup
Review my git commits from the past workday and generate a standup summary.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
start-development
Start development workflow process in Moira.
company-repo
Gestionar el repositorio Company Savia: crear, conectar, estado, sincronizar. El repositorio compartido de la empresa para conocimiento, mensajería y estado.
weekly-summary
Generate weekly work summary from git activity.