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/clear-subtasks/clear-subtasks.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/clear-subtasks)<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/clear-subtasks"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/clear-subtasks/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/clear-subtasks"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/clear-subtasks.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.00442 |
| Opus 5 | $0.00000 | $0.00221 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
clear-subtasks 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 10d 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
8 near-identical copies found in the catalogue:
- clear-subtasks — 100% identical, 0 lines differ
- remove-subtasks — 100% identical, 0 lines differ
- remove-subtasks — 100% identical, 0 lines differ
- clear-subtasks — 100% identical, 0 lines differ
- clear-subtasks — 100% identical, 0 lines differ
- remove-subtasks — 100% identical, 0 lines differ
- clear-subtasks — 100% identical, 3 lines differ
- clear-subtasks — 100% identical, 0 lines differ
What it actually says
Clear all subtasks from a specific task.
Arguments: $ARGUMENTS (task ID)
Remove all subtasks from a parent task at once.
Clearing Subtasks
Bulk removal of all subtasks from a parent task.
Execution
task-master clear-subtasks --id=<task-id>
Pre-Clear Analysis
-
Subtask Summary
- Number of subtasks
- Completion status of each
- Work already done
- Dependencies affected
-
Impact Assessment
- Data that will be lost
- Dependencies to be removed
- Effect on project timeline
- Parent task implications
Confirmation Required
Clear Subtasks Confirmation
━━━━━━━━━━━━━━━━━━━━━━━━━
Parent Task: #5 "Implement user authentication"
Subtasks to remove: 4
- #5.1 "Setup auth framework" (done)
- #5.2 "Create login form" (in-progress)
- #5.3 "Add validation" (pending)
- #5.4 "Write tests" (pending)
⚠️ This will permanently delete all subtask data
Continue? (y/n)
Smart Features
- Option to convert to standalone tasks
- Backup task data before clearing
- Preserve completed work history
- Update parent task appropriately
Process
- List all subtasks for confirmation
- Check for in-progress work
- Remove all subtasks
- Update parent task
- Clean up dependencies
Alternative Options
Suggest alternatives:
- Convert important subtasks to tasks
- Keep completed subtasks
- Archive instead of delete
- Export subtask data first
Post-Clear
- Show updated parent task
- Recalculate time estimates
- Update task complexity
- Suggest next steps
Example
/project:tm/clear-subtasks 5
→ Found 4 subtasks to remove
→ Warning: Subtask #5.2 is in-progress
→ Cleared all subtasks from task #5
→ Updated parent task estimates
→ Suggestion: Consider re-expanding with better breakdown
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.
- 10d ago First seen · 86 lines · 0 tokens per session scan A 13a6dbdac7d8
clear-subtasks 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 442 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.
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.
f5-jira
Jira integration - setup, sync, status, convert, issues, attachments.