Borrowing it
Nothing to install: this file belongs to zippoxer/subtask. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zippoxer/subtask/main/CLAUDE.mdgit 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/instructions/zippoxer/subtask/claude-md)<a href="https://agentmods.dev/instructions/zippoxer/subtask/claude-md"><img src="https://agentmods.dev/badge/instructions/zippoxer/subtask/claude-md/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/instructions/zippoxer/subtask/claude-md"><img src="https://agentmods.dev/badge/instructions/zippoxer/subtask/claude-md.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.02209 | $0.02209 |
| Opus 5.5 | $0.00884 | $0.00884 |
| Sonnet 5.5 | $0.00442 | $0.00442 |
| Haiku 4.5 | $0.00221 | $0.00221 |
Grade A, and why
subtask CLAUDE.md 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subtask
Parallel task management and orchestration for AI coding agents.
A lead agent dispatches work to parallel workers in isolated git worktrees, with context preservation and progress tracking.
Philosophy
The Problem
Without Subtask, a user managing multiple AI coding sessions must:
- Open multiple terminal tabs, each running Claude Code or Codex
- Mentally track what each session is working on
- Juggle progress, blockers, and dependencies in their head
- Re-explain context when sessions crash or expire
- Be the project manager while also trying to get work done
This cognitive load is exhausting. The user becomes a human orchestrator for AI workers.
The Solution
Subtask shifts the cognitive burden from user to lead agent.
Three roles:
- User: Gives direction, makes decisions, approves work
- Lead (e.g., Claude Code): Orchestrates everything in between
- Workers: Execute tasks in parallel, isolated in git worktrees
The user provides direction. The lead handles everything else: understanding requirements, breaking work into tasks, dispatching to workers, tracking progress, reviewing output, iterating until it's right, merging when ready.
The lead is not a task dispatcher. The lead is a technical lead / project manager. We're building tools that enable this.
Design Goals
Every feature should ask:
- Does this reduce cognitive load on the user?
- Is this simple for the lead to use and understand?
If a feature adds complexity for the user, it's probably wrong. If it confuses the lead, it's also wrong. Internal complexity is fine if the interface stays simple.
Design Decisions
- Task-centric — Task name is the primary identifier. Everything flows from it.
- Git-native — Branches for isolation, worktrees for parallelism, standard merge workflow.
- File-based collaboration — Task folder shared between lead and worker. PLAN.md for plans, PROGRESS.json for tracking. Files persist; sessions don't.
- Workspace opacity — Lead never picks workspaces. Subtask assigns them.
- Context preservation — Task folders are the portable, syncable unit. history.jsonl and
--follow-upensure nothing is lost when sessions crash. Copy anywhere, full context. Internal state and caches are local and rebuildable. - Progress visibility — Tool counts, timing, and PROGRESS.json let lead track workers without interrupting them.
- Guardrails over escape hatches — Prevent footguns. Errors guide the lead on what to do next, not just fail. Dangerous operations require explicit intent.
- Local-first — Operations use local git state. Lead controls when to sync with remote. No stale remote ref surprises.
- Event sourcing —
history.jsonlis the append-only source of truth. SQLite index is a derived projection for fast queries. If they diverge, history wins.
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 · 242 lines · 2,209 tokens per session scan A 6dc5c6b7b4cf
subtask CLAUDE.md is an instructions file published in the GitHub repository zippoxer/subtask (337 stars, last pushed 6mo ago), licensed MIT. It adds 2,209 tokens to every session, about $0.0088 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.