autotask-mcp: Command for Claude Code

.claude/commands/tm/set-status/to-in-progress.md

to-in-progress is a command for Claude Code from TICnine/autotask-mcp. It costs 0 tokens per session (190 once invoked), scanned A, a copy of to-in-progress, Apache-2.0.

A command that starts work on a task by changing its status to in-progress.

In plain words
What is it for?
Use it to begin a task while preparing related project context, such as a branch, documentation, test watchers, acceptance criteria, and possible blockers.
Why use it?
It checks basic readiness first, so work is less likely to begin with missing details or unmet dependencies.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is TICnine/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 TICnine/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/TICnine/autotask-mcp/main/.claude/commands/tm/set-status/to-in-progress.md
Clone the repo
git clone --depth 1 https://github.com/TICnine/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 to-in-progress

README.md
[![agentmods](https://agentmods.dev/badge/commands/ticnine/autotask-mcp/to-in-progress.svg)](https://agentmods.dev/commands/ticnine/autotask-mcp/to-in-progress)
Your own site
<a href="https://agentmods.dev/commands/ticnine/autotask-mcp/to-in-progress"><img src="https://agentmods.dev/badge/commands/ticnine/autotask-mcp/to-in-progress.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 190 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 100% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00190
Opus 5 $0.00000 $0.00095
Sonnet 5 $0.00000 $0.00038
Haiku 4.5 $0.00000 $0.00019

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

Security

Grade A, and why

to-in-progress 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 6d 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

100% identical to to-in-progress — 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.

.claude/commands/tm/set-status/to-in-progress.md · 36 lines

What it actually says

Start working on a task by setting its status to in-progress.

Arguments: $ARGUMENTS (task ID)

Starting Work on Task

This command does more than just change status - it prepares your environment for productive work.

Pre-Start Checks

  1. Verify dependencies are met
  2. Check if another task is already in-progress
  3. Ensure task details are complete
  4. Validate test strategy exists

Execution

task-master set-status --id=$ARGUMENTS --status=in-progress

Environment Setup

After setting to in-progress:

  1. Create/checkout appropriate git branch
  2. Open relevant documentation
  3. Set up test watchers if applicable
  4. Display task details and acceptance criteria
  5. Show similar completed tasks for reference

Smart Suggestions

  • Estimated completion time based on complexity
  • Related files from similar tasks
  • Potential blockers to watch for
  • Recommended first steps
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. 6d ago First seen · 36 lines · 0 tokens per session scan A 9df92c555844

Subscribe to this mod's changes

to-in-progress is a command published in the GitHub repository TICnine/autotask-mcp (0 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 190 tokens. A static security scan graded it A with 0 findings. It is 100% identical to to-in-progress, differing in 0 lines, and is treated as a copy.