Borrowing it
Nothing to install: this file belongs to MrJoeSack/pm-prompts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MrJoeSack/pm-prompts/main/.claude/commands/stakeholder-sync.mdgit 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/stakeholder-sync)<a href="https://agentmods.dev/commands/mrjoesack/pm-prompts/stakeholder-sync"><img src="https://agentmods.dev/badge/commands/mrjoesack/pm-prompts/stakeholder-sync.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.00013 | $0.00297 |
| Opus 5 | $0.00006 | $0.00148 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
stakeholder-sync 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 7d 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.
What it actually says
Stakeholder Sync Generator
Create stakeholder communication that moves work forward. Apply clarity principles:
Framework
Decision: What needs to happen?
Deadline: When?
Dependencies: What do you need from them?
Downside: What happens if we don't act?
Communication Rules
- Start with the ask (don't bury in paragraph 3)
- Cut ceremony ("I hope this finds you well")
- Use bullets for complex information
- End with clear next steps (who does what by when)
Quality Test
- Does this advance the work?
- Is the ask crystal clear?
- Are next steps actionable?
- Would you respond quickly to this message?
Input Template
Describe your situation like this: "I need [who] to [what action] because [why] by [when]"
Examples:
- "I need the legal team to approve our data collection approach because we want to ship analytics by month-end"
- "I need design leadership to sign off on simplified onboarding because engineering needs specs by Friday"
Output
Draft the communication, then provide a brief effectiveness analysis.
Arguments: {{args}}
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.
- 7d ago First seen · 43 lines · 13 tokens per session scan A 24864772bcd6
stakeholder-sync is a command published in the GitHub repository MrJoeSack/pm-prompts (6 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 297 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.