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 zippoxer/subtask --skill installgit clone --depth 1 https://github.com/zippoxer/subtaskWrote 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/zippoxer/subtask/install)<a href="https://agentmods.dev/skills/zippoxer/subtask/install"><img src="https://agentmods.dev/badge/skills/zippoxer/subtask/install/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/skills/zippoxer/subtask/install"><img src="https://agentmods.dev/badge/skills/zippoxer/subtask/install.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.00057 | $0.01157 |
| Opus 5.5 | $0.00023 | $0.00463 |
| Sonnet 5.5 | $0.00011 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
subtask 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 1mo 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subtask
Subtask is a CLI for orchestrating parallel AI workers. There are three roles: the user who gives direction, you (the lead) who orchestrates and delegates, and workers who execute tasks.
Each worker runs in an isolated git worktree. They can't conflict with each other.
The user tells you what they need. You clarify requirements, break work into tasks, dispatch to workers, review their output, iterate until it's right, and merge when ready.
Prefer to delegate exploration, research and planning to workers as parts of their tasks. Workers have time & space to dig deep, whereas you should preserve context to lead. Only go into details yourself when user explicitly requested, or the situation calls for it.
Mindset
- Understand before delegating — ask questions, clarify requirements. Don't rush to create tasks until you understand what the user actually wants.
- Own the complexity — stay on top of all tasks. Surface progress and blockers. Don't make the user chase status.
- Work autonomously — review output, request changes, iterate with workers. Only involve the user for decisions they need to make.
- Ask before merging — get user sign-off before merging. Don't merge without user approval.
Commands
| Command | Description |
|---|---|
subtask ask "..." |
Quick question (no task, runs in cwd) |
subtask draft <task> --base-branch <branch> --title "..." <<'EOF' |
Create a task |
subtask send <task> <prompt> |
Prompt worker on task (blocks until reply) |
subtask stage <task> <stage> |
Advance workflow stage |
subtask list |
View all tasks |
subtask show <task> |
View task details |
subtask diff [--stat] <task> |
Show changes (from merge base) |
subtask merge <task> -m "msg" |
Squash-merge task into base branch |
subtask close <task> |
Close without merging, free workspace |
subtask workspace <task> |
Get workspace path (a git worktree) |
subtask interrupt <task> |
Gracefully stop a running worker |
subtask log <task> |
Show task conversation and history |
subtask trace <task> |
Debug what a worker is doing and thinking internally |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 107 lines · 57 tokens per session scan A 476140dd6e44
subtask is a skill published in the GitHub repository zippoxer/subtask (337 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 1,157 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
product-launch-retail
A documented workflow for taking a new product from research and pricing through listing, sales, and an initial review. It uses shared templates, task records, and sales data files.
book-club
A structured workflow for running a book club, covering book selection, scheduling, preparation, discussion, and planning the next meeting.
cc-skill-project-guidelines-example
Project Guidelines Skill (Example).
ergo-backlog-planning
Shape multi-step work into Ergo tasks with a clear definition of done and a practical way to check it. Use when planning software, documentation, or other project work in an Ergo backlog. Skip small tasks and routine housekeeping.
gstack-sprint
3-Phase Sprint workflow — design → execute → review with user interaction at decision points.
grace-status
Show GRACE 4 project health across .grace context, graph, verification, active changes, scopes, and migration boundaries.