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 agentmods add commands/asachs01/float-mcp/clear-all-subtasksgit clone --depth 1 https://github.com/asachs01/float-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/asachs01/float-mcp/clear-all-subtasks)<a href="https://agentmods.dev/commands/asachs01/float-mcp/clear-all-subtasks"><img src="https://agentmods.dev/badge/commands/asachs01/float-mcp/clear-all-subtasks.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00450 |
| Opus 5 | $0.00000 | $0.00225 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
clear-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 4d 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.
This is a copy
100% identical to clear-all-subtasks — 6 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.
What it actually says
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
-
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 -
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
- Full project analysis
- Create backup file
- Show detailed impact
- Require confirmation
- Execute removal
- 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
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.
- 4d ago First seen · 97 lines · 0 tokens per session scan A 7214fb05681f
clear-all-subtasks is a command published in the GitHub repository asachs01/float-mcp (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 450 tokens. A static security scan graded it A with 0 findings. It is 100% identical to clear-all-subtasks, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
tasks
Break down the plan into executable tasks.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-status
Show governance health, wizard next step, all open blocking/high todos, and pending review count. Primary daily entry.
pm-charter
Create, import, discover, approve, or skip project charter. No-arg form is an interactive wizard.
_closing
会改 .pm/ 的 /pm- 回复必须有一句中文摘要。链接只列已经存在的文件，不要指向还没生成的路径。.
context-new
Create a new GitHub repository with AllBeads pre-configured.