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.
curl -O https://raw.githubusercontent.com/WYRE-AI/autotask-mcp/main/.claude/commands/tm/complexity-report/complexity-report.mdgit clone --depth 1 https://github.com/WYRE-AI/autotask-mcpWrote 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/wyre-ai/autotask-mcp/complexity-report)<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/complexity-report"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/complexity-report/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.
<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/complexity-report"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/complexity-report.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00604 |
| Opus 5.5 | $0.00000 | $0.00242 |
| Sonnet 5.5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
complexity-report 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 1mo 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.
Copies of this mod
7 near-identical copies found in the catalogue:
- complexity-report — 100% identical, 12 lines differ
- complexity-report — 100% identical, 0 lines differ
- complexity-report — 100% identical, 12 lines differ
- complexity-report — 100% identical, 0 lines differ
- complexity-report — 100% identical, 0 lines differ
- complexity-report — 100% identical, 0 lines differ
- complexity-report — 89% identical, 9 lines differ
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Display the task complexity analysis report.
Arguments: $ARGUMENTS
View the detailed complexity analysis generated by analyze-complexity command.
Viewing Complexity Report
Shows comprehensive task complexity analysis with actionable insights.
Execution
task-master complexity-report [--file=<path>]
Report Location
Default: .taskmaster/reports/complexity-analysis.md
Custom: Specify with --file parameter
Report Contents
1. Executive Summary
Complexity Analysis Summary
━━━━━━━━━━━━━━━━━━━━━━━━
Analysis Date: 2024-01-15
Tasks Analyzed: 32
High Complexity: 5 (16%)
Medium Complexity: 12 (37%)
Low Complexity: 15 (47%)
Critical Findings:
- 5 tasks need immediate expansion
- 3 tasks have high technical risk
- 2 tasks block critical path
2. Detailed Task Analysis
For each complex task:
- Complexity score breakdown
- Contributing factors
- Specific risks identified
- Expansion recommendations
- Similar completed tasks
3. Risk Matrix
Visual representation:
Risk vs Complexity Matrix
━━━━━━━━━━━━━━━━━━━━━━━
High Risk | #5(9) #12(8) | #23(6)
Med Risk | #34(7) | #45(5) #67(5)
Low Risk | #78(8) | [15 tasks]
| High Complex | Med Complex
4. Recommendations
Immediate Actions:
- Expand task #5 - Critical path + high complexity
- Expand task #12 - High risk + dependencies
- Review task #34 - Consider splitting
Sprint Planning:
- Don't schedule multiple high-complexity tasks together
- Ensure expertise available for complex tasks
- Build in buffer time for unknowns
Interactive Features
When viewing report:
-
Quick Actions
- Press 'e' to expand a task
- Press 'd' for task details
- Press 'r' to refresh analysis
-
Filtering
- View by complexity level
- Filter by risk factors
- Show only actionable items
-
Export Options
- Markdown format
- CSV for spreadsheets
- JSON for tools
Report Intelligence
- Compares with historical data
- Shows complexity trends
- Identifies patterns
- Suggests process improvements
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.
- 1mo ago First seen · 117 lines · 0 tokens per session scan A 772545699d24
complexity-report is a command published in the GitHub repository WYRE-AI/autotask-mcp (58 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 604 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.
Other commands, from other repositories
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.
umt-doctor
Diagnose UMT MCP server setup — builds, environment variables, and config health.
umt
Survey the Universal MCP Toolkit — available servers, install state, and how to connect them to any harness.
build_dashboard
Design & build a dense SaaS dashboard or app shell — navigation, tables, empty/loading states, a generated product-UI system — not a marketing page in disguise.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.