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.
git clone --depth 1 https://github.com/dtannen/pmWrote 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/dtannen/pm/prd-to-epic)<a href="https://agentmods.dev/commands/dtannen/pm/prd-to-epic"><img src="https://agentmods.dev/badge/commands/dtannen/pm/prd-to-epic/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/dtannen/pm/prd-to-epic"><img src="https://agentmods.dev/badge/commands/dtannen/pm/prd-to-epic.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.01070 |
| Opus 5 | $0.00005 | $0.00535 |
| Sonnet 5 | $0.00002 | $0.00214 |
| Haiku 4.5 | $0.00001 | $0.00107 |
Grade A, and why
prd-to-epic 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 8d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convert PRD to Epic
Transform a Product Requirements Document into a detailed technical implementation plan.
Usage
/pm:prd-to-epic <feature-name>
Instructions
You are creating a technical epic for: $ARGUMENTS
MCP Integration (preferred)
Ensure the epic exists in MCP and prime it for upcoming tasks.
- Full name: mcp__project-manager-mcp__list_epics — Check for existing epic
- Full name: mcp__project-manager-mcp__create_task — Upsert epic/project via a seed task
- Full name: mcp__project-manager-mcp__update_task — Record epic planning metadata/logs
Recommended flow:
- If the epic is not found via
...__list_epics, create a seed task withepic_name=$ARGUMENTSto upsert the epic. - Persist epic-level RA planning metadata (architecture decisions, risks) into
ra_metadata.epic_planattached to the seed task using...__update_task. - Proceed to
/pm:epic-tasks $ARGUMENTSto generate granular tasks backed by MCP.
1. Validate PRD Exists
- Check if
.pm/prds/$ARGUMENTS.mdexists - If not found: "❌ PRD not found. Create it first with: /pm:prd-new $ARGUMENTS"
- Read and analyze the PRD content
2. Technical Analysis
Based on the PRD, analyze:
Architecture Requirements
- What new database tables/models are needed?
- What API endpoints need to be created/modified?
- What UI components are required?
- How does this integrate with existing systems?
Data Flow Design
- How does data move through the system?
- What are the key data transformations?
- Where is data stored and how is it accessed?
- What are the performance implications?
Integration Points
- What external services are involved?
- How does this interact with authentication?
- What existing APIs need to be modified?
- Are there third-party integrations required?
3. Technology-Specific Planning
Read .pm/config.json to get the project type, then create architecture decisions specific to the tech stack:
For TypeScript Projects:
- React/Vue component architecture
- State management approach (Context, Redux, Zustand)
- API client structure
- TypeScript interfaces and types
- Build and bundling considerations
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.
- 8d ago First seen · 155 lines · 11 tokens per session scan A f5838a2f3e03
prd-to-epic is a command published in the GitHub repository dtannen/pm (0 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 1,070 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.