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/nextgit 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.00019 | $0.01630 |
| Opus 5 | $0.00010 | $0.00815 |
| Sonnet 5 | $0.00004 | $0.00326 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
next 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 yesterday.
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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get Next Priority Task
Intelligently recommend the next highest-priority task to work on based on dependencies, parallel opportunities, and project status.
Usage
/pm:next
Instructions
Analyze the current project state to recommend the optimal next task for execution.
MCP Integration (preferred)
Use MCP to identify available tasks and compute a recommendation.
- Full name: mcp__project-manager-mcp__get_available_tasks — Primary list of ready tasks
- Full name: mcp__project-manager-mcp__list_tasks — For additional filtering or scoring
- Full name: mcp__project-manager-mcp__get_task_details — Deep context for top candidates
Recommended flow:
- Call
mcp__project-manager-mcp__get_available_tasks(e.g., status=TODO, include_locked=false) to fetch candidates. - Score by: dependency readiness, RA score (complexity), epic priority, estimated hours, and recent activity.
- For the top 3 tasks, fetch
...__get_task_detailsand present concise rationales. - Provide a “start now” suggestion that points to
/pm:task-start <task>which will handle locking and status via MCP.
1. Scan Task Status
Read all tasks in .pm/tasks/ and categorize by status:
- Open: Available for execution
- In Progress: Currently being worked on
- Blocked: Waiting for dependencies
- Completed: Finished tasks
2. Dependency Analysis
For each open task:
- Check
depends_onfield for prerequisite tasks - Verify all dependencies are completed
- Identify tasks with no remaining dependencies (ready to start)
- Calculate dependency chain length for prioritization
3. Parallel Execution Opportunities
Identify tasks that can run simultaneously:
- Check
parallel: trueflag - Review
conflicts_withfield to avoid conflicts - Group compatible tasks for parallel execution
- Consider current in-progress tasks for conflict avoidance
4. Priority Scoring Algorithm
Score each available task based on:
Critical Path Impact (Weight: 40%)
- Tasks on critical path get highest priority
- Tasks blocking other tasks get bonus points
- Tasks with many dependents score higher
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.
- yesterday First seen · 232 lines · 19 tokens per session scan A d6d0c6e85c37
next is a command published in the GitHub repository dtannen/pm (0 stars, last pushed 10mo ago), licensed MIT. It adds 19 tokens to every session and 1,630 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.