Borrowing it
Nothing to install: this file belongs to vibehat/claude-task-manager. 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/vibehat/claude-task-manager/master/.claude/commands/tm/validate-dependencies/validate-dependencies.mdgit clone --depth 1 https://github.com/vibehat/claude-task-managerWrote 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/vibehat/claude-task-manager/validate-dependencies)<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/validate-dependencies"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/validate-dependencies.svg" alt="Measured on agentmods" 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.00348 |
| Opus 5 | $0.00000 | $0.00174 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
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 3d 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.
This is a copy
100% identical to validate-dependencies — 7 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.
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
-
Circular Dependencies
- A depends on B, B depends on A
- Complex circular chains
- Self-dependencies
-
Missing Dependencies
- References to non-existent tasks
- Deleted task references
- Invalid task IDs
-
Logical Issues
- Completed tasks depending on pending
- Cancelled tasks in dependency chains
- Impossible sequences
-
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-dependenciesto auto-fix - Manually adjust problematic dependencies
- Rerun to verify fixes
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.
- 3d ago First seen · 78 lines · 0 tokens per session scan A b36fcbbfd6e5
validate-dependencies is a command published in the GitHub repository vibehat/claude-task-manager (21 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 348 tokens. A static security scan graded it A with 0 findings. It is 100% identical to validate-dependencies, differing in 7 lines, and is treated as a copy.
Other commands, from other repositories
work
Execute Memory Bank workflow modes from pipeline.yaml — existing plan/spec execution by default, optional full-cycle requirements→plan→implementation→review flows.
sdd
Generate a Kiro-style spec triple — specs/ /{requirements,design,tasks}.md.
traceability-gen
Regenerate traceability.md from specs + plans + tests.
roadmap-sync
Regenerate roadmap.md autosync block from plans/.md frontmatter.
insert-phase
Insert urgent work as decimal phase (e.g., 72.1) between existing phases.
remove-phase
Remove a future phase from roadmap and renumber subsequent phases.