autotask-mcp: Command for Claude Code

.claude/commands/tm/validate-dependencies/validate-dependencies.md

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

A command that checks whether task dependencies are valid. A dependency means one task must be completed before another can proceed.

In plain words
What is it for?
Use it to produce a dependency report with errors, warnings, a task relationship graph, the critical path, bottlenecks, and suggested improvements.
Why use it?
It finds circular links, missing tasks, impossible sequences, overly complicated chains, and tasks that could block much of the project.

Command for Claude Code

Written for Claude Code: installed under .claude/.

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/validate-dependencies/validate-dependencies.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 validate-dependencies

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/validate-dependencies"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/validate-dependencies.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 347 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.00347
Opus 5 $0.00000 $0.00173
Sonnet 5 $0.00000 $0.00069
Haiku 4.5 $0.00000 $0.00035

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

Security

Grade A, and why

validate-dependencies 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/validate-dependencies/validate-dependencies.md · 71 lines

What it actually says

Validate all task dependencies for issues.

Dependency Validation

Comprehensive check for dependency problems across the entire project.

Execution

task-master validate-dependencies

Validation Checks

  1. Circular Dependencies

    • A depends on B, B depends on A
    • Complex circular chains
    • Self-dependencies
  2. Missing Dependencies

    • References to non-existent tasks
    • Deleted task references
    • Invalid task IDs
  3. Logical Issues

    • Completed tasks depending on pending
    • Cancelled tasks in dependency chains
    • Impossible sequences
  4. Complexity Warnings

    • Over-complex dependency chains
    • Too many dependencies per task
    • Bottleneck tasks

Smart Analysis

The validation provides:

  • Visual dependency graph
  • Critical path analysis
  • Bottleneck identification
  • Suggested optimizations

Report Format

Dependency Validation Report
━━━━━━━━━━━━━━━━━━━━━━━━━━
✅ No circular dependencies found
⚠️  2 warnings found:
   - Task #23 has 7 dependencies (consider breaking down)
   - Task #45 blocks 5 other tasks (potential bottleneck)
❌ 1 error found:
   - Task #67 depends on deleted task #66

Critical Path: #1 → #5 → #23 → #45 → #50 (15 days)

Actionable Output

For each issue found:

  • Clear description
  • Impact assessment
  • Suggested fix
  • Command to resolve

Next Steps

After validation:

  • Run /project:tm/fix-dependencies to auto-fix
  • Manually adjust problematic dependencies
  • Rerun to verify fixes
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 · 71 lines · 0 tokens per session scan A e59ad74ea338

Subscribe to this mod's changes

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