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/statusgit 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.00016 | $0.01573 |
| Opus 5 | $0.00008 | $0.00787 |
| Sonnet 5 | $0.00003 | $0.00315 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
status 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Status Dashboard
Display comprehensive overview of all PRDs, epics, and tasks with progress tracking.
Usage
/pm:status
Instructions
Generate a comprehensive project status dashboard.
MCP Integration (preferred)
Use MCP to fetch canonical project/epic/task data instead of filesystem scans.
- Full name: mcp__project-manager-mcp__list_projects
- Full name: mcp__project-manager-mcp__list_epics
- Full name: mcp__project-manager-mcp__list_tasks
- Full name: mcp__project-manager-mcp__get_available_tasks
- Full name: mcp__project-manager-mcp__get_task_details
Recommended flow:
- Fetch projects: list recent N via
mcp__project-manager-mcp__list_projects. - Fetch epics:
mcp__project-manager-mcp__list_epics(optionally per project) and compute epic counts by status. - Fetch tasks:
mcp__project-manager-mcp__list_tasks(optionally filter by project/epic/status) to compute counts and hours, and to build progress metrics. - Optionally use
mcp__project-manager-mcp__get_available_tasksto highlight next available work and parallel opportunities. - For spotlighted tasks, call
mcp__project-manager-mcp__get_task_detailsto surface RA metadata (mode, score, dependencies) and recent log entries.
If MCP is unavailable, fall back to filesystem-based scanning below.
1. Scan PM Directories
First, use find command or direct path access to locate the .pm directory:
find . -name ".pm" -type d
# Or use absolute path if needed
ls -la .pm/
Check for existence and content of:
.pm/prds/- Product Requirements Documents.pm/epics/- Technical implementation plans.pm/tasks/- Individual task files.pm/config.json- Project configuration
IMPORTANT: The .pm directory may be hidden. Use ls -la or find commands to locate it properly.
If directories don't exist: "⚠️ PM workflow not initialized. Run: /pm:init"
2. Collect PRD Status
For each file in .pm/prds/:
- Read frontmatter for status, created date, description
- Count total PRDs by status (backlog, in-progress, completed)
- Identify most recent PRD activity
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 · 194 lines · 16 tokens per session scan A ee73e74754e0
status is a command published in the GitHub repository dtannen/pm (0 stars, last pushed 10mo ago), licensed MIT. It adds 16 tokens to every session and 1,573 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.