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 GxFn/Wakeflow --skill wakeflow-target-craftgit 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-craft)<a href="https://agentmods.dev/skills/gxfn/wakeflow/wakeflow-target-craft"><img src="https://agentmods.dev/badge/skills/gxfn/wakeflow/wakeflow-target-craft.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.1 | $0.00025 | $0.03143 |
| Opus 5 | $0.00013 | $0.01571 |
| Sonnet 5 | $0.00005 | $0.00629 |
| Haiku 4.5 | $0.00003 | $0.00314 |
Grade A, and why
wakeflow-target-craft 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 7d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wakeflow Target Craft
Load this alongside wakeflow-target. wakeflow-target governs the immutable
dispatch packet, window boundaries, strict TargetResult recording, and return
transport — the "how do I interact with the state machine". THIS skill governs
the "how do I write the code well" so acceptance passes on the first pass
instead of looping through rework.
Core stance
The target must leave structured, reproducible REVIEW INPUTS, not a "looks done" claim. Wakeflow can check that required kinds and mappings exist and that exact declared ref/digest tuples are linked; it cannot establish that the referenced contents are true. Every craft practice below exists to give the controller something concrete to inspect and independently rerun before acceptance. Craft prepares an honest review; it does not earn acceptance by itself.
NO IMPLEMENTATION UNTIL EVERY AUTHORED acceptanceAnchor HAS A PLANNED RED TEST OR PROBE; NO COMPLETED RESULT UNTIL EVERY ANCHOR MAPS TO EXACT EVIDENCE REFS.
Violating the letter of this rule is violating its spirit.
- Read the package's
objective,requirementRefs, completeboundaries,completionExpectations,acceptanceAnchors, and advisorydesignIntentbefore planning code. - For each anchor, record
id -> test/probe seam -> expected RED -> expected GREEN. Use the exact confirmed claim; do not widen it. - If an anchor is untestable, conflicts with another authority, or requires
missing facts, return
needs-review. Never invent a replacement goal. - A newly authored implementation package without anchors is invalid and must
return
needs-review. Non-implementation packages (including research, documentation, and Test work) and read-only legacy compatibility packages may legitimately omit them; never create requirement authority yourself. - A Test dispatch packet may list this Skill because it carries a
reviewInputContract. In that case use only the evidence and result-shape guidance here; the packet'stestContract.executionContractand the target Skill's Test Alignment Gate stay authoritative, and the product implementation practices below do not widen Test's assignment.
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.
- 7d ago First seen · 272 lines · 25 tokens per session scan A 88708fcf6eb4
wakeflow-target-craft is a skill published in the GitHub repository GxFn/Wakeflow (5 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 3,143 once invoked, about $0.0001 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…
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…
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.