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/remove-subtaskgit clone --depth 1 https://github.com/asachs01/float-mcpWhat 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.00463 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
remove-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 yesterday.
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 remove-subtask — 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
Remove a subtask from its parent task.
Arguments: $ARGUMENTS
Parse subtask ID to remove, with option to convert to standalone task.
Removing Subtasks
Remove a subtask and optionally convert it back to a standalone task.
Argument Parsing
- "remove subtask 5.1"
- "delete 5.1"
- "convert 5.1 to task" → remove and convert
- "5.1 standalone" → convert to standalone
Execution Options
1. Delete Subtask
task-master remove-subtask --id=<parentId.subtaskId>
2. Convert to Standalone
task-master remove-subtask --id=<parentId.subtaskId> --convert
Pre-Removal Checks
-
Validate Subtask
- Verify subtask exists
- Check completion status
- Review dependencies
-
Impact Analysis
- Other subtasks that depend on it
- Parent task implications
- Data that will be lost
Removal Process
For Deletion:
- Confirm if subtask has work done
- Update parent task estimates
- Remove subtask and its data
- Clean up dependencies
For Conversion:
- Assign new standalone task ID
- Preserve all task data
- Update dependency references
- Maintain task history
Smart Features
- Warn if subtask is in-progress
- Show impact on parent task
- Preserve important data
- Update related estimates
Example Flows
/project:tm/remove-subtask 5.1
→ Warning: Subtask #5.1 is in-progress
→ This will delete all subtask data
→ Parent task #5 will be updated
Confirm deletion? (y/n)
/project:tm/remove-subtask 5.1 convert
→ Converting subtask #5.1 to standalone task #89
→ Preserved: All task data and history
→ Updated: 2 dependency references
→ New task #89 is now independent
Post-Removal
- Update parent task status
- Recalculate estimates
- Show updated hierarchy
- Suggest next actions
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.
- yesterday First seen · 90 lines · 0 tokens per session scan A 7cb06a9c3b5a
remove-subtask 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 463 tokens. A static security scan graded it A with 0 findings. It is 100% identical to remove-subtask, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
pm-arch
Scan project structure and generate Mermaid architecture diagrams + flowcharts under .pm/architecture/.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
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.
pm-check
Diagnose .pm/ health (missing files, broken audit, stale map, unconfirmed PRD) and repair or increment without overwriting confirmed content.