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/work-slicingnpx skills add GxFn/Wakeflow --skill work-slicinggit 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/work-slicing)<a href="https://agentmods.dev/skills/gxfn/wakeflow/work-slicing"><img src="https://agentmods.dev/badge/skills/gxfn/wakeflow/work-slicing.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.00030 | $0.00846 |
| Opus 5 | $0.00015 | $0.00423 |
| Sonnet 5 | $0.00006 | $0.00169 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
work-slicing 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 5d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Slicing
Convert a confirmed requirement design into controller-intake candidates. This skill proposes slices; it does not write the controller TODO board, create state roots, or dispatch windows.
Source Skills Used
mattpocock/skills/engineering/to-issues: tracer-bullet vertical slices, HITL/AFK marking, dependency order, user-story coverage, and granularity quiz.agile-product-owner: INVEST checks and acceptance criteria quality.- Industry basis: INVEST user story quality and vertical-slice delivery.
Wakeflow Role
Design proposes task-package candidates. Controller decides whether they enter TODO, state roots, waves, or dispatch. Use this skill when a requirement design is confirmed enough to discuss implementation chunks.
Interaction First
Default to conversation. Use this skill to propose candidate slices, explain dependencies, and ask the user/controller to confirm granularity and HITL/AFK labels before writing any tracked Design artifact.
Do not create or update slice notes, handoff drafts, TODO boards, task packages, or board rows as the first action. Write files only when the user/controller explicitly asks for a tracked artifact, confirms that the proposed content should be recorded, or a controller state root assigns a write deliverable. If a write is justified, state what will be written and why before editing.
Inputs
- Requirement design or PRD-like artifact.
- Confirmed non-goals and completion definition.
- Option-plan decision if multiple implementation routes existed.
- Current repository/window map when available.
- Known producer/consumer dependencies.
Vertical Slice Rules
Every candidate must be a thin but complete path through the necessary layers. It should be demoable, reviewable, or verifiable by itself.
Do not create horizontal slices such as:
- "define types";
- "add interface";
- "create adapter";
- "write tests later";
- "make provider shell";
- "cleanup docs";
- "wire plumbing without a consumer".
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.
- 5d ago First seen · 128 lines · 30 tokens per session scan A c1950707b954
work-slicing is a skill published in the GitHub repository GxFn/Wakeflow (5 stars, last pushed 11d ago), licensed MIT. It adds 30 tokens to every session and 846 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
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.
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.
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…
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.
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.