autotask-mcp: Command for Claude Code

.claude/commands/tm/status/project-status.md

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

An enhanced project-status command that summarises active work, progress, blockers, time estimates, and sprint or milestone status. A sprint is a short planned period of work, and a blocker is something preventing progress.

In plain words
What is it for?
Checking sprint progress, blocked tasks, team workload, timeline accuracy, project risks, task bottlenecks, quick wins, completion forecasts, and recommended task order.
Why use it?
It gathers scattered project information into a single status view and highlights delays, dependencies, workload issues, and delivery risks.

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/status/project-status.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 project-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/project-status/github.svg)](https://agentmods.dev/commands/wyre-ai/autotask-mcp/project-status)
Your own site
<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/project-status"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/project-status/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.

agentmods 80×15 button for project-status

Your own site · 80×15
<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/project-status"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/project-status.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 426 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.00426
Opus 5 $0.00000 $0.00213
Sonnet 5 $0.00000 $0.00085
Haiku 4.5 $0.00000 $0.00043

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

Security

Grade A, and why

project-status 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 9d 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/status/project-status.md · 64 lines

What it actually says

Enhanced status command with comprehensive project insights.

Arguments: $ARGUMENTS

Intelligent Status Overview

1. Executive Summary

Quick dashboard view:

  • 🏃 Active work (in-progress tasks)
  • 📊 Progress metrics (% complete, velocity)
  • 🚧 Blockers and risks
  • ⏱️ Time analysis (estimated vs actual)
  • 🎯 Sprint/milestone progress

2. Contextual Analysis

Based on $ARGUMENTS, focus on:

  • "sprint" → Current sprint progress and burndown
  • "blocked" → Dependency chains and resolution paths
  • "team" → Task distribution and workload
  • "timeline" → Schedule adherence and projections
  • "risk" → High complexity or overdue items

3. Smart Insights

Workflow Health:

  • Idle tasks (in-progress > 24h without updates)
  • Bottlenecks (multiple tasks waiting on same dependency)
  • Quick wins (low complexity, high impact)

Predictive Analytics:

  • Completion projections based on velocity
  • Risk of missing deadlines
  • Recommended task order for optimal flow

4. Visual Intelligence

Dynamic visualization based on data:

Sprint Progress: ████████░░ 80% (16/20 tasks)
Velocity Trend: ↗️ +15% this week
Blocked Tasks:  🔴 3 critical path items

Priority Distribution:
High:   ████████ 8 tasks (2 blocked)
Medium: ████░░░░ 4 tasks
Low:    ██░░░░░░ 2 tasks

5. Actionable Recommendations

Based on analysis:

  1. Immediate actions (unblock critical path)
  2. Today's focus (optimal task sequence)
  3. Process improvements (recurring patterns)
  4. Resource needs (skills, time, dependencies)

6. Historical Context

Compare to previous periods:

  • Velocity changes
  • Pattern recognition
  • Improvement areas
  • Success patterns to repeat
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. 9d ago First seen · 64 lines · 0 tokens per session scan A c7da48edf158

Subscribe to this mod's changes

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