tm

A command for planning, starting, reviewing, and closing tasks through Task Master. It can turn a described change into a plan and then progress through ready tasks, using subagents or teammates when available.

In plain words
What is it for?
Use it to create a project plan from a request, run all ready tasks for a tag, manage task status, delegate implementation and reviews, and close completed work.
Why use it?
It coordinates multi-step development work instead of requiring each task to be managed manually. It also supports review loops and automatic pull-request merging when its stated conditions are met.

Command

Install

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.

agentmods
npx agentmods add commands/bjcoombs/ai-native-toolkit/tm
Clone the repo
git clone --depth 1 https://github.com/bjcoombs/ai-native-toolkit
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,479 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.03479
Opus 5 $0.00006 $0.01740
Sonnet 5 $0.00003 $0.00696
Haiku 4.5 $0.00001 $0.00348

Measured 2d ago against content hash 59de16190b9c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tm 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 2d 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.

commands/tm.md · 413 lines

How it starts

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

Task Master Orchestrator

$ARGUMENTS

Thin orchestrator. Delegates to subagents for implementation and review loops.

Planning Mode (/tm use stripe as kyc provider): When args don't match an existing tag, explores the codebase, writes a PRD, creates a tag, generates tasks, runs complexity analysis, and expands. Stops after planning - run /tm <tag> to start work.

Marathon Mode (/tm <tag>): When only a tag is given (no task-id), automatically progress through all ready tasks. When Agent Teams are available, each task gets its own teammate with shared task list. When teams unavailable, falls back to parallel subagents. PRs auto-merge when CI green, no conflicts, required approvals met, and 0 changes requested.


TM Work-Source Adapter

This command supplies the marathon skill's adapter as:

  • enumeratetask-master tags use "<tag>" && task-master list --json; use jq on tasks.json for reliable status filtering (task-master next can suggest subtask IDs of done parents).
  • mark in-progresstask-master set-status --id=<id> --status=in-progress (run sequentially inline — never as a parallel background job; concurrent TM writes race the global tag).
  • close on mergetask-master tags use "<tag>" && task-master set-status --id=<id> --status=done.
  • branch / worktree — branch <tag>--<task-id>--<slug>; worktree worktree/<tag>/<task-id>--<slug>.

Phase 0: Detect Capabilities

# Agent Teams
echo $CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS

Set $TEAMS_AVAILABLE (true if result is "1").

Project-Specific Configuration

Read the repo's CLAUDE.md for a ## Marathon Configuration section. This provides project-specific overrides for marathon behavior. Extract these values (with defaults if section is missing):

Setting Default Description
$BASE_BRANCH main Branch to create worktrees from and merge PRs into
$REQUIRED_APPROVALS 1 Minimum approvals for auto-merge
$MARKDOWN_APPROVALS 1 Approvals for markdown-only PRs
$RETRO_LOG (none) Path to retrospective log file
Bot reviewer rules (none) Per-bot thread resolution patterns
CI patterns (none) Known flaky checks, pre-existing failures

Read the full file on GitHub · 413 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. 2d ago First seen · 413 lines · 0 tokens per session scan A 59de16190b9c

Subscribe to this mod's changes

tm is a command published in the GitHub repository bjcoombs/ai-native-toolkit (30 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 3,479 once invoked, about $0.0001 per session on Opus 5. 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.