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/next/next-task.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/next-task)<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/next-task"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/next-task/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.
<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/next-task"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/next-task.svg" alt="Reviewed on agentmods" width="80" 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.00414 |
| Opus 5.5 | $0.00000 | $0.00166 |
| Sonnet 5.5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
next-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 1mo 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 next-task — 12 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
Intelligently determine and prepare the next action based on comprehensive context.
This enhanced version of 'next' considers:
- Current task states
- Recent activity
- Time constraints
- Dependencies
- Your working patterns
Arguments: $ARGUMENTS
Intelligent Next Action
1. Context Gathering
Let me analyze the current situation:
- Active tasks (in-progress)
- Recently completed tasks
- Blocked tasks
- Time since last activity
- Arguments provided: $ARGUMENTS
2. Smart Decision Tree
If you have an in-progress task:
- Has it been idle > 2 hours? → Suggest resuming or switching
- Near completion? → Show remaining steps
- Blocked? → Find alternative task
If no in-progress tasks:
- Unblocked high-priority tasks? → Start highest
- Complex tasks need breakdown? → Suggest expansion
- All tasks blocked? → Show dependency resolution
Special arguments handling:
- "quick" → Find task < 2 hours
- "easy" → Find low complexity task
- "important" → Find high priority regardless of complexity
- "continue" → Resume last worked task
3. Preparation Workflow
Based on selected task:
- Show full context and history
- Set up development environment
- Run relevant tests
- Open related files
- Show similar completed tasks
- Estimate completion time
4. Alternative Suggestions
Always provide options:
- Primary recommendation
- Quick alternative (< 1 hour)
- Strategic option (unblocks most tasks)
- Learning option (new technology/skill)
5. Workflow Integration
Seamlessly connect to:
/project:task-master:start [selected]/project:workflows:auto-implement/project:task-master:expand(if complex)/project:utils:complexity-report(if unsure)
The goal: Zero friction from decision to implementation.
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.
- 1mo ago First seen · 76 lines · 0 tokens per session scan A aa6087d7c9d5
next-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 414 tokens. A static security scan graded it A with 0 findings. It is 100% identical to next-task, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
work
A command that runs an existing Memory Bank workflow for planning, implementing, checking, reviewing, and completing development work. The workflow can use project plans or specification tasks.
sdd
A command that creates three connected planning files for a software feature: requirements, design, and tasks.
team
A team workflow command that splits one task into parallel tracks while keeping their work in a shared project tree. It assigns roles, records reports and locks, and coordinates scoped commits through a central board.
rules
A command for managing coding rules stored in CLAUDE.md, AGENTS.md, and optional project RULES.md files. It can select built-in rules, add personal rules, change settings such as architecture or coverage, and control whether test-driven development (TDD) is required.
roadmap-sync
A command that rebuilds the automatic sections of `roadmap.md` from plan files and their front matter, which is metadata at the top of a Markdown file.
traceability-gen
A command that rebuilds a Markdown table linking requirements to project plans and tests. It reads requirement files, plan files, and test markers, then records what is planned or covered.