remove-all-subtasks

A command that removes every subtask from every task in a project. Subtasks are smaller work items grouped under a larger task.

In plain words
What is it for?
Clearing all subtasks globally after reviewing what will be lost and confirming the destructive operation.
Why use it?
It clears the project's entire subtask structure, including completed and in-progress work, so it is intended only for deliberate project restructuring or a fresh start.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/sakrut/ai-code-graph/remove-all-subtasks
Clone the repo
git clone --depth 1 https://github.com/sakrut/ai-code-graph

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 454 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00454
Opus 5 $0.00000 $0.00227
Sonnet 5 $0.00000 $0.00091
Haiku 4.5 $0.00000 $0.00045

Measured 2d ago against content hash e3ae1153961d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

remove-all-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 2d 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.

Origin

This is a copy

95% identical to clear-all-subtasks — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/tm/remove-all-subtasks.md · 94 lines

What it actually says

Remove All Subtasks Clear all subtasks from all tasks globally.

Global Subtask Clearing

Remove all subtasks across the entire project. Use with extreme caution.

Execution

task-master clear-subtasks --all

Pre-Clear Analysis

  1. Project-Wide Summary

    Global Subtask Summary
    ━━━━━━━━━━━━━━━━━━━━
    Total parent tasks: 12
    Total subtasks: 47
    - Completed: 15
    - In-progress: 8
    - Pending: 24
    
    Work at risk: ~120 hours
    
  2. Critical Warnings

    • In-progress subtasks that will lose work
    • Completed subtasks with valuable history
    • Complex dependency chains
    • Integration test results

Double Confirmation

⚠️  DESTRUCTIVE OPERATION WARNING ⚠️
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This will remove ALL 47 subtasks from your project
Including 8 in-progress and 15 completed subtasks

This action CANNOT be undone

Type 'CLEAR ALL SUBTASKS' to confirm:

Smart Safeguards

  • Require explicit confirmation phrase
  • Create automatic backup
  • Log all removed data
  • Option to export first

Use Cases

Valid reasons for global clear:

  • Project restructuring
  • Major pivot in approach
  • Starting fresh breakdown
  • Switching to different task organization

Process

  1. Full project analysis
  2. Create backup file
  3. Show detailed impact
  4. Require confirmation
  5. Execute removal
  6. Generate summary report

Alternative Suggestions

Before clearing all:

  • Export subtasks to file
  • Clear only pending subtasks
  • Clear by task category
  • Archive instead of delete

Post-Clear Report

Global Subtask Clear Complete
━━━━━━━━━━━━━━━━━━━━━━━━━━━
Removed: 47 subtasks from 12 tasks
Backup saved: .taskmaster/backup/subtasks-20240115.json
Parent tasks updated: 12
Time estimates adjusted: Yes

Next steps:
- Review updated task list
- Re-expand complex tasks as needed
- Check project timeline
Changes

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.

  1. 2d ago First seen · 94 lines · 0 tokens per session scan A e3ae1153961d

Subscribe to this mod's changes

remove-all-subtasks is a command published in the GitHub repository sakrut/ai-code-graph (3 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 454 tokens. A static security scan graded it A with 0 findings. It is 95% identical to clear-all-subtasks, differing in 3 lines, and is treated as a copy.