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/wyre-ai/autotask-mcp/remove-subtaskgit 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/remove-subtask)<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/remove-subtask"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/remove-subtask.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.00462 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00092 |
| 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 5d 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
7 near-identical copies found in the catalogue:
- remove-subtask — 100% identical, 0 lines differ
- remove-subtask — 100% identical, 0 lines differ
- remove-subtask — 100% identical, 0 lines differ
- remove-subtask — 100% identical, 6 lines differ
- remove-subtask — 100% identical, 6 lines differ
- remove-subtask — 100% identical, 0 lines differ
- remove-subtask — 95% identical, 7 lines differ
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.
- 5d ago First seen · 84 lines · 0 tokens per session scan A d3497cdbdd40
remove-subtask is a command published in the GitHub repository WYRE-AI/autotask-mcp (50 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 462 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
build_dashboard
Design & build a dense SaaS dashboard or app shell — navigation, tables, empty/loading states, a generated product-UI system — not a marketing page in disguise.
zooza-setup
One-time Zooza setup — teaches Claude your business vocabulary so it understands your terms in every future session.
docs
Keep @README.md, @READMEru.md, @CLAUDE.md, and @CHANGELOG.md in sync with the actual yandex-wiki-search-mcp codebase.
browse
You have access to a browser via the MCP Browser Bridge tools. Use them to interact with web pages.
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.
bump-version-minor
Bump the minor version number in lib/cf/mcp/version.rb (e.g., 1.2.3 -> 1.3.0).