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.
npx agentmods add commands/asachs01/float-mcp/validate-dependenciesgit clone --depth 1 https://github.com/asachs01/float-mcpWhat 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 | $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 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.
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.
- 2d ago First seen · 78 lines · 0 tokens per session scan A b36fcbbfd6e5
validate-dependencies is a command published in the GitHub repository asachs01/float-mcp (2 stars, last pushed 6mo 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
pm-init
Initialize local .pm governance; detect Spec Kit; if absent, analyze the repo and draft a PRD for user confirmation; after confirm/skip run a technical light scan.
pm-all
Full technical governance scan; rebuild .pm/dashboard. Default does not wait on draft PRD. Use --compare-baseline only after a confirmed PRD/charter.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-export
Export desensitized governance summary markdown for sharing or machine switch.
pm-outline
Generate detailed project outline and draft charter from user intent (empty/new projects).
pm-status
Show governance health, wizard next step, all open blocking/high todos, and pending review count. Primary daily entry.