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/to-in-progressgit 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/to-in-progress)<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/to-in-progress"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/to-in-progress.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.00191 |
| Opus 5 | $0.00000 | $0.00096 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
to-in-progress 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 to-in-progress — 2 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
Start working on a task by setting its status to in-progress.
Arguments: $ARGUMENTS (task ID)
Starting Work on Task
This command does more than just change status - it prepares your environment for productive work.
Pre-Start Checks
- Verify dependencies are met
- Check if another task is already in-progress
- Ensure task details are complete
- Validate test strategy exists
Execution
task-master set-status --id=$ARGUMENTS --status=in-progress
Environment Setup
After setting to in-progress:
- Create/checkout appropriate git branch
- Open relevant documentation
- Set up test watchers if applicable
- Display task details and acceptance criteria
- Show similar completed tasks for reference
Smart Suggestions
- Estimated completion time based on complexity
- Related files from similar tasks
- Potential blockers to watch for
- Recommended first steps
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 · 38 lines · 0 tokens per session scan A 09fbda05b599
to-in-progress 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 191 tokens. A static security scan graded it A with 0 findings. It is 100% identical to to-in-progress, differing in 2 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.
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.
iniciar
Inicializar Don Cheli en un proyecto nuevo o existente.