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/helpgit 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.02920 |
| Opus 5 | $0.00006 | $0.01460 |
| Sonnet 5 | $0.00003 | $0.00584 |
| Haiku 4.5 | $0.00001 | $0.00292 |
Grade A, and why
help 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Adaptive Workflow Help
Comprehensive guide to the PM Adaptive Workflow - an intelligent task management system that automatically adjusts complexity handling based on task requirements.
Usage
/pm:help [command]
PM Adaptive Workflow Overview
The PM Adaptive Workflow transforms software development from one-size-fits-all to intelligent complexity scaling:
PRD → Epic → Tasks → Adaptive Execution → Quality-Matched Verification → Shipping
Core Philosophy
- Intelligent Scaling: Automatically match workflow rigor to task complexity
- No Wasted Effort: Simple tasks get simple treatment, complex tasks get thorough handling
- Assumption Awareness: Track and validate uncertainties in complex work
- Learning System: Get smarter over time through pattern recognition
- Quality Assurance: Appropriate verification for each complexity level
Adaptive Modes
The system automatically selects from four workflow modes:
Simple Mode (Complexity 1-3)
For: Bug fixes, simple UI changes, single-file modifications Process: Direct implementation → Basic testing → Done Duration: < 4 hours Overhead: Minimal
Standard Mode (Complexity 4-6)
For: Multi-file features, basic integrations, moderate complexity
Process: Plan → Implement → Test → Verify → Done
Duration: 4-8 hours
Overhead: Structured approach
RA-Light Mode (Complexity 7-8)
For: Cross-domain work, API integrations, significant refactoring Process: Assess → Plan → Tagged Implementation → Assumption Verification → Done Duration: 8-16 hours Overhead: Response Awareness tags and verification
RA-Full Mode (Complexity 9-10)
For: Architecture changes, complex integrations, mission-critical features Process: Survey → Multi-agent Planning → Synthesis → Orchestrated Implementation → Full Verification → Done Duration: > 16 hours Overhead: Complete Response Awareness orchestration
Command Reference
🚀 Getting Started
/pm:init- Initialize adaptive workflow with intelligent templates/pm:help- Show this help (or/pm:help <command>for details)
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 · 361 lines · 13 tokens per session scan A 6d3d1b8660d3
help 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 2,920 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.