autotask-mcp: Command for Claude Code

.claude/commands/tm/update/update-single-task.md

update-single-task is a command for Claude Code from WYRE-AI/autotask-mcp. It costs 0 tokens per session (589 once invoked), scanned A, original, Apache-2.0.

A command for changing one task using its ID and a plain-language instruction.

In plain words
What is it for?
Use it to revise a task’s description, requirements, acceptance criteria, priority, estimate, dependencies, implementation notes, test approach, or subtasks.
Why use it?
It helps update task details without manually finding and editing each field, while keeping the existing task information consistent.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is WYRE-AI/autotask-mcp's own configuration. It tells Claude Code how to work on autotask-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything autotask-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/WYRE-AI/autotask-mcp/main/.claude/commands/tm/update/update-single-task.md
Clone the repo
git clone --depth 1 https://github.com/WYRE-AI/autotask-mcp

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.

agentmods badge for update-single-task

README.md
[![agentmods](https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/update-single-task.svg)](https://agentmods.dev/commands/wyre-ai/autotask-mcp/update-single-task)
Your own site
<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/update-single-task"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/update-single-task.svg" alt="Measured on agentmods" 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 589 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 original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00589
Opus 5 $0.00000 $0.00295
Sonnet 5 $0.00000 $0.00118
Haiku 4.5 $0.00000 $0.00059

Measured 7d ago against content hash 253677d72ace, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

update-single-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 7d 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

Copies of this mod

7 near-identical copies found in the catalogue:

.claude/commands/tm/update/update-single-task.md · 119 lines

How it starts

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

Update a single specific task with new information.

Arguments: $ARGUMENTS

Parse task ID and update details.

Single Task Update

Precisely update one task with AI assistance to maintain consistency.

Argument Parsing

Natural language updates:

  • "5: add caching requirement"
  • "update 5 to include error handling"
  • "task 5 needs rate limiting"
  • "5 change priority to high"

Execution

task-master update-task --id=<id> --prompt="<context>"

Update Types

1. Content Updates

  • Enhance description
  • Add requirements
  • Clarify details
  • Update acceptance criteria

2. Metadata Updates

  • Change priority
  • Adjust time estimates
  • Update complexity
  • Modify dependencies

3. Strategic Updates

  • Revise approach
  • Change test strategy
  • Update implementation notes
  • Adjust subtask needs

AI-Powered Updates

The AI:

  1. Understands Context

    • Reads current task state
    • Identifies update intent
    • Maintains consistency
    • Preserves important info
  2. Applies Changes

    • Updates relevant fields
    • Keeps style consistent
    • Adds without removing
    • Enhances clarity
  3. Validates Results

    • Checks coherence
    • Verifies completeness
    • Maintains relationships
    • Suggests related updates

Example Updates

/project:tm/update/single 5: add rate limiting
→ Updating Task #5: "Implement API endpoints"

Current: Basic CRUD endpoints
Adding: Rate limiting requirements

Updated sections:
✓ Description: Added rate limiting mention
✓ Details: Added specific limits (100/min)
✓ Test Strategy: Added rate limit tests
✓ Complexity: Increased from 5 to 6
✓ Time Estimate: Increased by 2 hours

Suggestion: Also update task #6 (API Gateway) for consistency?

Smart Features

  1. Incremental Updates

    • Adds without overwriting
    • Preserves work history
    • Tracks what changed
    • Shows diff view
  2. Consistency Checks

    • Related task alignment
    • Subtask compatibility
    • Dependency validity
    • Timeline impact

Read the full file on GitHub · 119 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.

  1. 7d ago First seen · 119 lines · 0 tokens per session scan A 253677d72ace

Subscribe to this mod's changes

update-single-task is a command published in the GitHub repository WYRE-AI/autotask-mcp (50 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 589 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.