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/penwyp/claudepreference/m-task-plannergit clone --depth 1 https://github.com/penwyp/ClaudePreferenceWhat 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.00689 |
| Opus 5 | $0.00000 | $0.00345 |
| Sonnet 5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
m-task-planner 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Task Plan Workflow: Structure Implementation & Tests
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project)
Scope: Analyze requirements and generate structured implementation plan with tests
Execution Steps
-
Requirements Analysis
- Parse target documents and extract functional requirements
- Identify technical constraints and dependencies
- Document ambiguities and unclear specifications
-
Implementation Strategy Design
- Define architecture patterns and system design
- Plan API structures and data models
- Outline testing strategy and coverage approach
-
Task Decomposition
- Break down features into actionable implementation tasks
- Create corresponding test tasks for each feature
- Define task types (feature, test, refactor, documentation)
-
Dependency Mapping
- Identify task prerequisites and blocking relationships
- Sequence tasks based on logical dependencies
- Optimize for parallel development opportunities
-
Plan Visualization
- Generate Mermaid diagram showing task flow
- Illustrate critical path and milestone dependencies
- Highlight testing integration points
-
Generate Task Plan Report
- Compile findings into structured markdown format
- Save to
docs/workspaces/task-plan-MM-dd-HH-mm-ss.md
Output Format
English Report
overview
- High-level implementation strategy and architectural approach
- Testing methodology and coverage targets
- Key technical decisions and assumptions
tasks
Array of task objects with structure:
{
"id": "string",
"description": "string",
"type": "feature|test|refactor|docs",
"status": "pending|in-progress|completed",
"dependencies": ["task_id_1", "task_id_2"]
}
diagram
Mermaid diagram code illustrating:
- Task dependencies and flow
- Critical path identification
- Parallel execution opportunities
clarifications
Array of questions for requirement ambiguities:
- Unclear functional requirements
- Missing technical specifications
- Integration and compatibility concerns
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.
- 2d ago First seen · 109 lines · 0 tokens per session scan A 46e0abb50f2d
m-task-planner is a command published in the GitHub repository penwyp/ClaudePreference (137 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 689 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).