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-taskgit 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.00554 |
| Opus 5 | $0.00000 | $0.00277 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
remove-task 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-task — 9 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove a task permanently from the project.
Arguments: $ARGUMENTS (task ID)
Delete a task and handle all its relationships properly.
Task Removal
Permanently removes a task while maintaining project integrity.
Argument Parsing
- "remove task 5"
- "delete 5"
- "5" → remove task 5
- Can include "-y" for auto-confirm
Execution
task-master remove-task --id=<id> [-y]
Pre-Removal Analysis
-
Task Details
- Current status
- Work completed
- Time invested
- Associated data
-
Relationship Check
- Tasks that depend on this
- Dependencies this task has
- Subtasks that will be removed
- Blocking implications
-
Impact Assessment
Task Removal Impact ━━━━━━━━━━━━━━━━━━ Task: #5 "Implement authentication" (in-progress) Status: 60% complete (~8 hours work) Will affect: - 3 tasks depend on this (will be blocked) - Has 4 subtasks (will be deleted) - Part of critical path ⚠️ This action cannot be undone
Smart Warnings
- Warn if task is in-progress
- Show dependent tasks that will be blocked
- Highlight if part of critical path
- Note any completed work being lost
Removal Process
- Show comprehensive impact
- Require confirmation (unless -y)
- Update dependent task references
- Remove task and subtasks
- Clean up orphaned dependencies
- Log removal with timestamp
Alternative Actions
Suggest before deletion:
- Mark as cancelled instead
- Convert to documentation
- Archive task data
- Transfer work to another task
Post-Removal
- List affected tasks
- Show broken dependencies
- Update project statistics
- Suggest dependency fixes
- Recalculate timeline
Example Flows
/project:tm/remove-task 5
→ Task #5 is in-progress with 8 hours logged
→ 3 other tasks depend on this
→ Suggestion: Mark as cancelled instead?
Remove anyway? (y/n)
/project:tm/remove-task 5 -y
→ Removed: Task #5 and 4 subtasks
→ Updated: 3 task dependencies
→ Warning: Tasks #7, #8, #9 now have missing dependency
→ Run /project:tm/fix-dependencies to resolve
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 · 112 lines · 0 tokens per session scan A c3c145765d7d
remove-task 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 554 tokens. A static security scan graded it A with 0 findings. It is 100% identical to remove-task, differing in 9 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.