phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.
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.
git clone --depth 1 https://github.com/phuryn/pm-skillsWrote 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/phuryn/pm-skills/stakeholder-map)<a href="https://agentmods.dev/commands/phuryn/pm-skills/stakeholder-map"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/stakeholder-map.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.00014 | $0.00790 |
| Opus 5 | $0.00007 | $0.00395 |
| Sonnet 5 | $0.00003 | $0.00158 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
stakeholder-map 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- stakeholder-map — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/stakeholder-map -- Stakeholder Mapping & Communication Plan
Identify all stakeholders for a project, map them by influence and interest, and generate a communication plan that ensures the right people get the right information at the right time.
Invocation
/stakeholder-map New analytics platform launch
/stakeholder-map Pricing model change affecting all customers
/stakeholder-map [upload a project brief or org chart]
Workflow
Step 1: Understand the Initiative
Ask:
- What is the project or initiative?
- What phase is it in? (planning, building, launching, post-launch)
- Who are the obvious stakeholders you already know about?
- Are there any politically sensitive dynamics to be aware of?
Step 2: Identify Stakeholders
Brainstorm stakeholders the user might not have considered:
- Internal: Engineering, Design, QA, Data, Legal, Finance, Marketing, Sales, Support, Leadership
- External: Customers, partners, vendors, regulators, board members
- Often missed: Adjacent teams, on-call engineers, customer success, documentation team
Step 3: Map to Power × Interest Grid
Apply the stakeholder-map skill:
Place each stakeholder in a quadrant:
HIGH INTEREST
│
KEEP SATISFIED │ MANAGE CLOSELY
(High Power, │ (High Power,
Low Interest) │ High Interest)
│
──────────────────────┼──────────────────────
│
MONITOR │ KEEP INFORMED
(Low Power, │ (Low Power,
Low Interest) │ High Interest)
│
LOW INTEREST
Step 4: Generate Communication Plan
## Stakeholder Map: [Initiative]
### Stakeholder Grid
| Stakeholder | Role | Power | Interest | Quadrant | Stance |
|------------|------|-------|----------|----------|--------|
### Communication Plan
#### Manage Closely (High Power, High Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|
#### Keep Satisfied (High Power, Low Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|
#### Keep Informed (Low Power, High Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|
#### Monitor (Low Power, Low Interest)
[Minimal communication — include in broad updates only]
### Potential Conflicts
[Where stakeholder interests may clash — with mitigation strategies]
### Escalation Path
[Who to go to when decisions are blocked]
### RACI Matrix
| Decision Area | Responsible | Accountable | Consulted | Informed |
|--------------|-------------|-------------|-----------|----------|
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 · 108 lines · 14 tokens per session scan A 7db95fcb143d
stakeholder-map is a command published in the GitHub repository phuryn/pm-skills (26,033 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 790 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-30.
Other commands, from other repositories
retro
Facilitate a post-launch or sprint retrospective anchored to OKRs.
discover
Run a full discovery cycle — problem framing, JTBD demand-side analysis, assumption mapping, opportunity sizing, and OST mapping — from a rough idea to validated opportunity.
plan-sprint
Plan the upcoming sprint — epic breakdown, user story decomposition, RICE prioritization, dependency check, and capacity allocation.
roadmap
Build or review your roadmap — OKR alignment, Now/Next/Later structuring, dependency mapping, and stakeholder views, pulling live Linear/Jira state.
set-okrs
Structure OKRs — define objectives, write measurable key results, align to strategy, stress-test for quality, and cascade across teams.
triage-feedback
Triage a batch of user feedback — cluster themes, score by frequency × severity × strategic fit, route top issues to roadmap or experiments.