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/phj128/autoworker/subtask-initnpx skills add phj128/autoworker --skill subtask-initgit clone --depth 1 https://github.com/phj128/autoworkerWrote 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/phj128/autoworker/subtask-init)<a href="https://agentmods.dev/skills/phj128/autoworker/subtask-init"><img src="https://agentmods.dev/badge/skills/phj128/autoworker/subtask-init.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.00049 | $0.01167 |
| Opus 5 | $0.00024 | $0.00583 |
| Sonnet 5 | $0.00010 | $0.00233 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
subtask-init 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
autoworker:subtask-init — Create Subtask First Half (Gate 1.3 Step A+B)
After Plan Mode discussion is complete and user has confirmed direction, invoke this skill to create the first half of subtask.md.
Execution Flow
1. Determine Sequence Number
Glob `subtask_*.md` (current directory) + Glob `claude_docs/subtask/*.md` (archive)
→ Extract all sequence numbers → take max + 1
2. Extract Confirmation Record from Conversation Context
Review the conversation and extract:
- Confirmation method: AskUserQuestion / confirmed in plan discussion / explicit in user instruction
- Key Q&A: scope, completion criteria, constraints, preferences
- Goal: WHY + WHAT (1-3 sentences)
- Success criteria: specific measurable items
- Acceptance criteria: Extract quantifiable metrics from plan (metric name + measurement method + expected value/range + tolerance). When no quantitative metrics exist, explicitly write "No quantitative metrics, reason: "
3. Identify Core Assumptions
Extract assumptions that depend on external systems from plan and conversation. Each assumption needs:
- Assumption description (I assume X because Y)
- Verification experiment (one-line command)
Pure internal logic changes (e.g., refactoring, documentation): Write one line No external dependencies | — | —.
4. Search for Reference Files
Glob/Grep search for related files → confirm paths and line numbers
Do not guess line numbers — must Read to confirm.
5. Extract Design Decisions and Plan
Extract from plan file / conversation:
- Design decisions (decision point + choice + reason)
- Implementation plan (Phase/Step structure)
5.5. Pause Old Active Subtask
Glob `subtask_*.md` (exclude subtask_template.md) →
For each file grep `status: active` →
Edit all found to `status: paused`
Purpose: Ensure at most 1 active subtask at any time. Creating a new subtask automatically pauses old ones.
6. Write Subtask First Half
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 · 123 lines · 49 tokens per session scan A ff4ff170df5b
subtask-init is a skill published in the GitHub repository phj128/autoworker (17 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 1,167 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-30.
Other skills, from other repositories
flow-next-interview
In-depth Q&A to refine a spec, task, or spec file before building. Use when asked to flesh out, refine, or interrogate requirements.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-guide
Recommend the smallest sufficient flow-next workflow from the starting state. Stateless router. Use when unsure which command or stage applies next.
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.