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/mrjoesack/pm-prompts/pm-examplesgit clone --depth 1 https://github.com/MrJoeSack/pm-promptsWrote 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/mrjoesack/pm-prompts/pm-examples)<a href="https://agentmods.dev/commands/mrjoesack/pm-prompts/pm-examples"><img src="https://agentmods.dev/badge/commands/mrjoesack/pm-prompts/pm-examples.svg" alt="Measured on agentmods" 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.00009 | $0.00476 |
| Opus 5 | $0.00005 | $0.00238 |
| Sonnet 5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
pm-examples 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 5d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Command Examples
Scenario: Weekly Stakeholder Update
Situation: Need to update VP on project status
Steps:
- Type:
/stakeholder-sync - Input: "I need to update the VP on mobile app progress because we're behind schedule and need to discuss resource options by Friday"
- Get: Structured email with clear ask and next steps
Scenario: Feature Planning Session
Situation: Engineering wants clearer requirements
Steps:
- Type:
/feature-spec - Input: "We need to add user notifications because customers miss important updates so that engagement improves"
- Get: Structured PRD with problem/solution/success/trade-offs
Scenario: Quarterly Planning Prep
Situation: Strategy doc needs review before leadership meeting
Steps:
- Type:
/strategy-check - Paste your Q2 strategy document
- Get: Analysis using Rumelt's framework with specific improvement suggestions
Scenario: Difficult Engineering Conversation
Situation: Timeline negotiation with tech lead
Steps:
- Type:
/difficult-conversation - Input: "Engineering says the timeline is impossible but we committed to customers"
- Get: Structured conversation approach with opening and framework
Scenario: Executive Presentation
Situation: Need budget approval from C-suite
Steps:
- Type:
/exec-presentation - Input: "Need $500K for user research team expansion"
- Get: Slide structure with ask/why/how/evidence format
Quick Wins
Email that's too long: /stakeholder-sync then paste email
Vague feature idea: /feature-spec then describe the idea
Strategy that feels off: /strategy-check then paste strategy
Any PM document: /prd-review then paste content
Framework Chaining
Complete workflow example:
/quarterly-planning- Plan Q2 strategy/feature-spec- Define key features/stakeholder-sync- Get engineering buy-in/exec-presentation- Present to leadership/difficult-conversation- Handle objections
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.
- 5d ago First seen · 68 lines · 9 tokens per session scan A e3f1f83a003e
pm-examples is a command published in the GitHub repository MrJoeSack/pm-prompts (6 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 476 once invoked, about $0.0000 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.