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/generate/generate-tasks.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/generate-tasks)<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/generate-tasks"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/generate-tasks/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/generate-tasks"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/generate-tasks.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.00558 |
| Opus 5.5 | $0.00000 | $0.00223 |
| Sonnet 5.5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
generate-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 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 generate-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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate individual task files from tasks.json.
Task File Generation
Creates separate markdown files for each task, perfect for AI agents or documentation.
Execution
task-master generate
What It Creates
For each task, generates a file like task_001.txt:
Task ID: 1
Title: Implement user authentication
Status: pending
Priority: high
Dependencies: []
Created: 2024-01-15
Complexity: 7
## Description
Create a secure user authentication system with login, logout, and session management.
## Details
- Use JWT tokens for session management
- Implement secure password hashing
- Add remember me functionality
- Include password reset flow
## Test Strategy
- Unit tests for auth functions
- Integration tests for login flow
- Security testing for vulnerabilities
- Performance tests for concurrent logins
## Subtasks
1.1 Setup authentication framework (pending)
1.2 Create login endpoints (pending)
1.3 Implement session management (pending)
1.4 Add password reset (pending)
File Organization
Creates structure:
.taskmaster/
└── tasks/
├── task_001.txt
├── task_002.txt
├── task_003.txt
└── ...
Smart Features
-
Consistent Formatting
- Standardized structure
- Clear sections
- AI-readable format
- Markdown compatible
-
Contextual Information
- Full task details
- Related task references
- Progress indicators
- Implementation notes
-
Incremental Updates
- Only regenerate changed tasks
- Preserve custom additions
- Track generation timestamp
- Version control friendly
Use Cases
- AI Context: Provide task context to AI assistants
- Documentation: Standalone task documentation
- Archival: Task history preservation
- Sharing: Send specific tasks to team members
- Review: Easier task review process
Generation Options
Based on arguments:
- Filter by status
- Include/exclude completed
- Custom templates
- Different formats
Post-Generation
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 · 126 lines · 0 tokens per session scan A 42d34895dc6a
generate-tasks 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 558 tokens. A static security scan graded it A with 0 findings. It is 100% identical to generate-tasks, differing in 5 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.