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-targetnpx skills add GxFn/Wakeflow --skill wakeflow-targetgit 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/skills/gxfn/wakeflow/wakeflow-target)<a href="https://agentmods.dev/skills/gxfn/wakeflow/wakeflow-target"><img src="https://agentmods.dev/badge/skills/gxfn/wakeflow/wakeflow-target.svg" alt="Measured on agentmods" 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 | $0.00045 | $0.02118 |
| Opus 5 | $0.00023 | $0.01059 |
| Sonnet 5 | $0.00009 | $0.00424 |
| Haiku 4.5 | $0.00005 | $0.00212 |
Grade A, and why
wakeflow-target 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 4d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wakeflow Target
Use this skill only inside the target window named by the current delivery.
Workspace and repository CLAUDE.md files remain hard boundaries. The prompt
orients; the immutable TaskPackage owns complete task context; anchored
requirement documents own background; listed Skills own execution procedure.
Prompt Shape
Target wakeups stay task-first and compact:
Continue current window task: <currentWindow> / <taskId>.
Current objective (the task package is authoritative):
- <one-line objective>
Completion focus (up to two; full criteria are in the task package):
- <bounded observable result>
- <optional second bounded observable result>
- Priority context: <highest-priority confirmed fact>
- Critical boundary [forbidden|outOfScope|inScope]: <highest-priority boundary>
Key acceptance anchors (full probes and expectations are in the task package):
- <anchor id>: <claim>
Read before execution, in order:
- Task package (complete task context): <absolute package path>
- Requirement background entry: <document#section>
- Workspace instructions (only when distinct from repository instructions): <workspace>/CLAUDE.md
- Repository instructions: <repository>/CLAUDE.md
- Current state root: <absolute state-root path>
Required execution Skills (execution-process authority):
- skills/wakeflow-target/SKILL.md
- <other package-selected Skill>
Identity (full boundaries are in the task package):
- Current responsibility window: <window>
- Only working repository: <absolute repository path>
Before coding: map every `acceptanceAnchors` entry to a RED test or probe; return
needs-review instead of inventing a requirement when an anchor cannot be tested.
Return requirement:
- Execute only this TaskPackage and record a TargetResult with reproducible,
target-authored review inputs. It is never controller acceptance.
- Test execution contract: <dispatch packet path>#testContract.executionContract
Dispatch record (routing and trace only):
- taskId: <taskId>
- taskPackageId: <package>
- stateRoot: <path>
- stateRevision: <revision>
- dispatchGroup: <group>
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.
- 4d ago First seen · 198 lines · 45 tokens per session scan A c9da56cb43cd
wakeflow-target is a skill published in the GitHub repository GxFn/Wakeflow (5 stars, last pushed 11d ago), licensed MIT. It adds 45 tokens to every session and 2,118 once invoked, about $0.0002 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.
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.
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…
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".
evolve
Research-driven multi-cycle improvement director. Forms causal hypotheses about why scores are low, validates them with scout agents before attacking, dispatches axis-parallel fleet attacks, extracts transferable patterns, and runs indefinitely within a budget envelope. Accumulates a persistent belief model and…