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/workflows/auto-implement-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/auto-implement-tasks)<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/auto-implement-tasks"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/auto-implement-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.1 | $0.00000 | $0.00469 |
| Opus 5 | $0.00000 | $0.00234 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
auto-implement-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 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 auto-implement-tasks — 11 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhanced auto-implementation with intelligent code generation and testing.
Arguments: $ARGUMENTS
Intelligent Auto-Implementation
Advanced implementation with context awareness and quality checks.
1. Pre-Implementation Analysis
Before starting:
- Analyze task complexity and requirements
- Check codebase patterns and conventions
- Identify similar completed tasks
- Assess test coverage needs
- Detect potential risks
2. Smart Implementation Strategy
Based on task type and context:
Feature Tasks
- Research existing patterns
- Design component architecture
- Implement with tests
- Integrate with system
- Update documentation
Bug Fix Tasks
- Reproduce issue
- Identify root cause
- Implement minimal fix
- Add regression tests
- Verify side effects
Refactoring Tasks
- Analyze current structure
- Plan incremental changes
- Maintain test coverage
- Refactor step-by-step
- Verify behavior unchanged
3. Code Intelligence
Pattern Recognition
- Learn from existing code
- Follow team conventions
- Use preferred libraries
- Match style guidelines
Test-Driven Approach
- Write tests first when possible
- Ensure comprehensive coverage
- Include edge cases
- Performance considerations
4. Progressive Implementation
Step-by-step with validation:
Step 1/5: Setting up component structure ✓
Step 2/5: Implementing core logic ✓
Step 3/5: Adding error handling ⚡ (in progress)
Step 4/5: Writing tests ⏳
Step 5/5: Integration testing ⏳
Current: Adding try-catch blocks and validation...
5. Quality Assurance
Automated checks:
- Linting and formatting
- Test execution
- Type checking
- Dependency validation
- Performance analysis
6. Smart Recovery
If issues arise:
- Diagnostic analysis
- Suggestion generation
- Fallback strategies
- Manual intervention points
- Learning from failures
7. Post-Implementation
After completion:
- Generate PR description
- Update documentation
- Log lessons learned
- Suggest follow-up tasks
- Update task relationships
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 · 108 lines · 0 tokens per session scan A e8c76b6ce8bd
auto-implement-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 469 tokens. A static security scan graded it A with 0 findings. It is 100% identical to auto-implement-tasks, differing in 11 lines, and is treated as a copy.
Other commands, from other repositories
tdd
Start test-driven development workflow for a feature or fix.
config
Complete configuration guide for pair programming sessions.
start
Start a new pair programming session with AI assistance.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
cpp-test
Enforce TDD workflow for C++. Write GoogleTest tests first, then implement. Verify coverage with gcov/lcov.
go-test
Go TDD workflow with table-driven tests.