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/list-tasksgit 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/list-tasks)<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/list-tasks"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/list-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 | $0.00000 | $0.00373 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
list-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 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 list-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.
What it actually says
List tasks with intelligent argument parsing.
Parse arguments to determine filters and display options:
- Status: pending, in-progress, done, review, deferred, cancelled
- Priority: high, medium, low (or priority:high)
- Special: subtasks, tree, dependencies, blocked
- IDs: Direct numbers (e.g., "1,3,5" or "1-5")
- Complex: "pending high" = pending AND high priority
Arguments: $ARGUMENTS
Let me parse your request intelligently:
-
Detect Filter Intent
- If arguments contain status keywords → filter by status
- If arguments contain priority → filter by priority
- If arguments contain "subtasks" → include subtasks
- If arguments contain "tree" → hierarchical view
- If arguments contain numbers → show specific tasks
- If arguments contain "blocked" → show blocked tasks only
-
Smart Combinations Examples of what I understand:
- "pending high" → pending tasks with high priority
- "done today" → tasks completed today
- "blocked" → tasks with unmet dependencies
- "1-5" → tasks 1 through 5
- "subtasks tree" → hierarchical view with subtasks
-
Execute Appropriate Query Based on parsed intent, run the most specific task-master command
-
Enhanced Display
- Group by relevant criteria
- Show most important information first
- Use visual indicators for quick scanning
- Include relevant metrics
-
Intelligent Suggestions Based on what you're viewing, suggest next actions:
- Many pending? → Suggest priority order
- Many blocked? → Show dependency resolution
- Looking at specific tasks? → Show related tasks
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 · 48 lines · 0 tokens per session scan A a9ee1bd6f94a
list-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 373 tokens. A static security scan graded it A with 0 findings. It is 100% identical to list-tasks, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
paul:add-phase
Add a new phase to current milestone.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
check_schema_version
Check the Flyway schema version of the SQLite database on a Docker volume.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
cycle-design
Design a cycle — create new cycles with planned stories, detail existing planning cycles, or quick-sketch a roadmap. Detects planning docs in .craft/planning/ and sources the cycle from them when relevant.
cycle-start
Activate a cycle and start implementing its stories.