Borrowing it
Nothing to install: this file belongs to WYRE-AI/autotask-mcp. 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/WYRE-AI/autotask-mcp/main/.claude/commands/tm/add-subtask/add-subtask.mdgit clone --depth 1 https://github.com/WYRE-AI/autotask-mcpWrote 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/commands/wyre-ai/autotask-mcp/add-subtask)<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/add-subtask"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/add-subtask/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/commands/wyre-ai/autotask-mcp/add-subtask"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/add-subtask.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.00000 | $0.00456 |
| Opus 5 | $0.00000 | $0.00228 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
add-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 9d 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.
Copies of this mod
7 near-identical copies found in the catalogue:
- add-subtask — 100% identical, 0 lines differ
- add-subtask — 100% identical, 0 lines differ
- add-subtask — 100% identical, 8 lines differ
- add-subtask — 100% identical, 0 lines differ
- add-subtask — 100% identical, 0 lines differ
- add-subtask — 100% identical, 8 lines differ
- add-subtask — 94% identical, 9 lines differ
What it actually says
Add a subtask to a parent task.
Arguments: $ARGUMENTS
Parse arguments to create a new subtask or convert existing task.
Adding Subtasks
Creates subtasks to break down complex parent tasks into manageable pieces.
Argument Parsing
Flexible natural language:
- "add subtask to 5: implement login form"
- "break down 5 with: setup, implement, test"
- "subtask for 5: handle edge cases"
- "5: validate user input" → adds subtask to task 5
Execution Modes
1. Create New Subtask
task-master add-subtask --parent=<id> --title="<title>" --description="<desc>"
2. Convert Existing Task
task-master add-subtask --parent=<id> --task-id=<existing-id>
Smart Features
-
Automatic Subtask Generation
- If title contains "and" or commas, create multiple
- Suggest common subtask patterns
- Inherit parent's context
-
Intelligent Defaults
- Priority based on parent
- Appropriate time estimates
- Logical dependencies between subtasks
-
Validation
- Check parent task complexity
- Warn if too many subtasks
- Ensure subtask makes sense
Creation Process
- Parse parent task context
- Generate subtask with ID like "5.1"
- Set appropriate defaults
- Link to parent task
- Update parent's time estimate
Example Flows
/project:tm/add-subtask to 5: implement user authentication
→ Created subtask #5.1: "implement user authentication"
→ Parent task #5 now has 1 subtask
→ Suggested next subtasks: tests, documentation
/project:tm/add-subtask 5: setup, implement, test
→ Created 3 subtasks:
#5.1: setup
#5.2: implement
#5.3: test
Post-Creation
- Show updated task hierarchy
- Suggest logical next subtasks
- Update complexity estimates
- Recommend subtask order
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.
- 9d ago First seen · 76 lines · 0 tokens per session scan A 6afcb2773455
add-subtask is a command published in the GitHub repository WYRE-AI/autotask-mcp (50 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 456 tokens. 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 commands, from other repositories
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.
daily-standup
Génération Résumé Daily Stand-up.
task-management
Query and update recorded planning and research portfolio state across tasks, topics, papers, outputs, submissions, venues, people, institutions, and deadlines. Use when asking what is already recorded, including institution- or venue-associated topics, or when doing daily planning and weekly review. For venue…
parallel
You are executing the /hydra:parallel command. Start multiple agents simultaneously in different worktrees.
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.