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/dtannen/pm/epic-tasksgit clone --depth 1 https://github.com/dtannen/pmWhat 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.00013 | $0.03771 |
| Opus 5 | $0.00006 | $0.01886 |
| Sonnet 5 | $0.00003 | $0.00754 |
| Haiku 4.5 | $0.00001 | $0.00377 |
Grade A, and why
epic-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 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 — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Break Epic into Granular Tasks
Transform a technical epic into specific, actionable tasks with detailed implementation plans.
Usage
/pm:epic-tasks <feature-name>
Instructions
You are breaking down the epic for: $ARGUMENTS
MCP Integration (preferred)
Use MCP to validate epic context and create tasks with structured metadata.
- Full name: mcp__project-manager-mcp__list_epics
- Full name: mcp__project-manager-mcp__list_tasks
- Full name: mcp__project-manager-mcp__create_task
- Full name: mcp__project-manager-mcp__update_task
Recommended flow:
- Validate epic exists by name via
mcp__project-manager-mcp__list_epics(or by id if known). - For each granular task, create it with
mcp__project-manager-mcp__create_taskusingepic_name=$ARGUMENTSand initialra_metadata(acceptance criteria, file list, dependencies) plus parallel execution fields:parallel_group,conflicts_with, andparallel_eligible. - For RA planning blocks, persist planning details in
ra_metadata.planningviamcp__project-manager-mcp__update_task. - CRITICAL: Include proper
dependenciesfield (task ID array) and parallel execution metadata to enable agent coordination. - Optionally mirror task files into
.pm/tasks/for local context; MCP remains the source of truth.
1. Validate Epic Exists
- Prefer MCP: verify via
mcp__project-manager-mcp__list_epicsby name; error if not found. - Optionally read
.pm/epics/$ARGUMENTS.mdfor additional context.
2. Task Breakdown Philosophy
CRITICAL: No Vague Tasks Allowed
Every task must be:
- 2-8 hours maximum (no exceptions)
- Concrete and specific (exact files, functions, components to build)
- Independently executable (minimal dependencies)
- Clearly testable (specific success criteria)
- One logical unit of work (single feature/component/endpoint)
Bad Task Examples (DON'T DO THIS):
- ❌ "Implement user management"
- ❌ "Add authentication"
- ❌ "Create API endpoints"
- ❌ "Build frontend"
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 · 425 lines · 13 tokens per session scan A e2b0e08b808d
epic-tasks is a command published in the GitHub repository dtannen/pm (0 stars, last pushed 10mo ago), licensed MIT. It adds 13 tokens to every session and 3,771 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.