What is update-tasks-from-id?

A command that applies a new requirement or context change to a group of tasks starting at a given task ID. It includes related tasks, dependent tasks, or subtasks within logical boundaries.

Use it to revise descriptions, test plans, estimates, dependencies, or implementation details across a related set of tasks while preserving completed work.

It keeps related planning information aligned when a change affects more than one task.

How sakrut/ai-code-graph configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to sakrut/ai-code-graph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sakrut/ai-code-graph/main/.claude/commands/tm/update-tasks-from-id.md

Clone the repo

git clone --depth 1 https://github.com/sakrut/ai-code-graph

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sakrut/ai-code-graph/update-tasks-from-id/github.svg)](https://agentmods.dev/commands/sakrut/ai-code-graph/update-tasks-from-id)

Your own site

<a href="https://agentmods.dev/commands/sakrut/ai-code-graph/update-tasks-from-id"><img src="https://agentmods.dev/badge/commands/sakrut/ai-code-graph/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sakrut/ai-code-graph/update-tasks-from-id"><img src="https://agentmods.dev/badge/commands/sakrut/ai-code-graph/update-tasks-from-id.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 558 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 92% copy Near-identical to another mod in the catalogue.

Token cost

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.00558
Opus 5.5	$0.00000	$0.00223
Sonnet 5.5	$0.00000	$0.00112
Haiku 4.5	$0.00000	$0.00056

Measured 1mo ago against content hash 7f4d44feb043, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

This is a copy

92% identical to update-tasks-from-id — 11 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.

.claude/commands/tm/update-tasks-from-id.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update Tasks From ID

Arguments: $ARGUMENTS 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

/taskmaster:update-tasks-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

Read the full file on GitHub · 111 lines

Changes

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.

1mo ago First seen · 111 lines · 0 tokens per session scan A 7f4d44feb043

Subscribe to this mod's changes

update-tasks-from-id is a command published in the GitHub repository sakrut/ai-code-graph (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 558 tokens. A static security scan graded it A with 0 findings. It is 92% identical to update-tasks-from-id, differing in 11 lines, and is treated as a copy.

Project management

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

fest-show

Show festival progression (in-progress tasks, roadmap, and dependency view).

Obedience-Corp/festival · 17 tokens

add-note

Add an internal or external note to a ConnectWise PSA ticket.

WYRE-AI/msp-claude-plugins · 12 tokens

dispatcher

Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…

Kanevry/session-orchestrator · 185 tokens

sync-linear

Sync current work with Linear ticket status.

bybren-llc/safe-agentic-workflow · 0 tokens

plc-project-status

Read .claude/skills/plc-project-status/SKILL.md and execute its official procedure. Target: $ARGUMENTS.

miyatti777/ai-plc · 14 tokens

ai-code-graph: Command for Claude Code