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/vibehat/claude-task-manager/expand-taskgit 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/expand-task)<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/expand-task"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/expand-task.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.00249 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
expand-task 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 expand-task — 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
Break down a complex task into subtasks.
Arguments: $ARGUMENTS (task ID)
Intelligent Task Expansion
Analyzes a task and creates detailed subtasks for better manageability.
Execution
task-master expand --id=$ARGUMENTS
Expansion Process
-
Task Analysis
- Review task complexity
- Identify components
- Detect technical challenges
- Estimate time requirements
-
Subtask Generation
- Create 3-7 subtasks typically
- Each subtask 1-4 hours
- Logical implementation order
- Clear acceptance criteria
-
Smart Breakdown
- Setup/configuration tasks
- Core implementation
- Testing components
- Integration steps
- Documentation updates
Enhanced Features
Based on task type:
- Feature: Setup → Implement → Test → Integrate
- Bug Fix: Reproduce → Diagnose → Fix → Verify
- Refactor: Analyze → Plan → Refactor → Validate
Post-Expansion
After expansion:
- Show subtask hierarchy
- Update time estimates
- Suggest implementation order
- Highlight critical path
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 · 54 lines · 0 tokens per session scan A dee13d993e20
expand-task 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 249 tokens. A static security scan graded it A with 0 findings. It is 100% identical to expand-task, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
deploy_to_docker
Build Docker image and start/redeploy the MCP Task Orchestrator container, reusing the last-used config by default.
check_schema_version
Check the Flyway schema version of the SQLite database on a Docker volume.
paul:help
Show available PAUL commands and usage guide.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
adr
You are helping create a new ADR (Architecture Decision Record). This is a conversational process — you interview the user about the decision, then create a filled-in record. ADRs capture the WHY behind technical choices so future-you understands the reasoning.
status
Dashboard — auth ready, billing, usage, last session.