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/expand-all-tasksgit clone --depth 1 https://github.com/asachs01/float-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/asachs01/float-mcp/expand-all-tasks)<a href="https://agentmods.dev/commands/asachs01/float-mcp/expand-all-tasks"><img src="https://agentmods.dev/badge/commands/asachs01/float-mcp/expand-all-tasks.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 | $0.00000 | $0.00218 |
| Opus 5 | $0.00000 | $0.00109 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
expand-all-tasks 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 5d 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 expand-all-tasks — 5 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
Expand all pending tasks that need subtasks.
Bulk Task Expansion
Intelligently expands all tasks that would benefit from breakdown.
Execution
task-master expand --all
Smart Selection
Only expands tasks that:
- Are marked as pending
- Have high complexity (>5)
- Lack existing subtasks
- Would benefit from breakdown
Expansion Process
-
Analysis Phase
- Identify expansion candidates
- Group related tasks
- Plan expansion strategy
-
Batch Processing
- Expand tasks in logical order
- Maintain consistency
- Preserve relationships
- Optimize for parallelism
-
Quality Control
- Ensure subtask quality
- Avoid over-decomposition
- Maintain task coherence
- Update dependencies
Options
- Add
forceto expand all regardless of complexity - Add
researchfor enhanced AI analysis
Results
After bulk expansion:
- Summary of tasks expanded
- New subtask count
- Updated complexity metrics
- Suggested task order
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.
- 5d ago First seen · 56 lines · 0 tokens per session scan A f8e129088f1c
expand-all-tasks 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 218 tokens. A static security scan graded it A with 0 findings. It is 100% identical to expand-all-tasks, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
tasks
Break down the plan into executable tasks.
plan
Plan how to implement the specified feature.
specify
Start a new feature by creating a specification and feature branch.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
new
Creates a new item in a module that supports the new capability.
ingest-dev
Ingest a URL, directory, or file into your knowledge base. remember = a specific durable fact, ingest = a URL, learn = a distilled lesson that gets retrieval preference.