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/snarktank/code-editing-agent/update-tasks-from-idgit clone --depth 1 https://github.com/snarktank/code-editing-agentWrote 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/snarktank/code-editing-agent/update-tasks-from-id)<a href="https://agentmods.dev/commands/snarktank/code-editing-agent/update-tasks-from-id"><img src="https://agentmods.dev/badge/commands/snarktank/code-editing-agent/update-tasks-from-id.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.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 4d 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.
This is a copy
100% identical to update-tasks-from-id — 0 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 — 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.
- 4d ago First seen · 108 lines · 0 tokens per session scan A c1155613b0bd
update-tasks-from-id is a command published in the GitHub repository snarktank/code-editing-agent (24 stars, last pushed 1y ago), licensed MIT. 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. It is 100% identical to update-tasks-from-id, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.