Borrowing it
Nothing to install: this file belongs to WYRE-AI/autotask-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WYRE-AI/autotask-mcp/main/.claude/commands/tm/update/update-tasks-from-id.mdgit 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/update-tasks-from-id)<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/update-tasks-from-id"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/update-tasks-from-id/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/update-tasks-from-id"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/update-tasks-from-id.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00547 |
| Opus 5 | $0.00000 | $0.00273 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
update-tasks-from-id 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 11d 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:
- update-tasks-from-id — 100% identical, 15 lines differ
- update-tasks-from-id — 100% identical, 0 lines differ
- update-tasks-from-id — 100% identical, 15 lines differ
- update-tasks-from-id — 100% identical, 0 lines differ
- update-tasks-from-id — 100% identical, 0 lines differ
- update-tasks-from-id — 100% identical, 0 lines differ
- update-tasks-from-id — 92% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update multiple tasks starting from a specific ID.
Arguments: $ARGUMENTS
Parse starting task ID and update context.
Bulk Task Updates
Update multiple related tasks based on new requirements or context changes.
Argument Parsing
- "from 5: add security requirements"
- "5 onwards: update API endpoints"
- "starting at 5: change to use new framework"
Execution
task-master update --from=<id> --prompt="<context>"
Update Process
1. Task Selection
Starting from specified ID:
- Include the task itself
- Include all dependent tasks
- Include related subtasks
- Smart boundary detection
2. Context Application
AI analyzes the update context and:
- Identifies what needs changing
- Maintains consistency
- Preserves completed work
- Updates related information
3. Intelligent Updates
- Modify descriptions appropriately
- Update test strategies
- Adjust time estimates
- Revise dependencies if needed
Smart Features
-
Scope Detection
- Find natural task groupings
- Identify related features
- Stop at logical boundaries
- Avoid over-updating
-
Consistency Maintenance
- Keep naming conventions
- Preserve relationships
- Update cross-references
- Maintain task flow
-
Change Preview
Bulk Update Preview ━━━━━━━━━━━━━━━━━━ Starting from: Task #5 Tasks to update: 8 tasks + 12 subtasks Context: "add security requirements" Changes will include: - Add security sections to descriptions - Update test strategies for security - Add security-related subtasks where needed - Adjust time estimates (+20% average) Continue? (y/n)
Example Updates
/project:tm/update/from-id 5: change database to PostgreSQL
→ Analyzing impact starting from task #5
→ Found 6 related tasks to update
→ Updates will maintain consistency
→ Preview changes? (y/n)
Applied updates:
✓ Task #5: Updated connection logic references
✓ Task #6: Changed migration approach
✓ Task #7: Updated query syntax notes
✓ Task #8: Revised testing strategy
✓ Task #9: Updated deployment steps
✓ Task #12: Changed backup procedures
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.
- 11d ago First seen · 108 lines · 0 tokens per session scan A c1155613b0bd
update-tasks-from-id 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 547 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
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
daily-standup
Génération Résumé Daily Stand-up.
task-management
Query and update recorded planning and research portfolio state across tasks, topics, papers, outputs, submissions, venues, people, institutions, and deadlines. Use when asking what is already recorded, including institution- or venue-associated topics, or when doing daily planning and weekly review. For venue…
parallel
You are executing the /hydra:parallel command. Start multiple agents simultaneously in different worktrees.
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.
f5-jira
Jira integration - setup, sync, status, convert, issues, attachments.