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 skills add julianoczkowski/product-manager --skill pm-stakeholder-communicationgit clone --depth 1 https://github.com/julianoczkowski/product-managerWrote 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/skills/julianoczkowski/product-manager/pm-stakeholder-communication)<a href="https://agentmods.dev/skills/julianoczkowski/product-manager/pm-stakeholder-communication"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-stakeholder-communication/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/julianoczkowski/product-manager/pm-stakeholder-communication"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-stakeholder-communication.svg" alt="Reviewed on agentmods" width="80" 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.00107 | $0.01198 |
| Opus 5 | $0.00053 | $0.00599 |
| Sonnet 5 | $0.00021 | $0.00240 |
| Haiku 4.5 | $0.00011 | $0.00120 |
Grade A, and why
pm-stakeholder-communication 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 11d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Communications (Pragmatic Framework: Planning → Stakeholder Communications)
Executives communicate in spreadsheets, not screenshots. Track trends, not absolute numbers. Manage proactive communications from strategy through execution.
See ../pm-copilot/references/framework.md for the primitives.
Three steps
Identify → Analyze → Communicate.
- Identify every stakeholder or group affected by or influencing the work.
- Analyze each on two axes and place them on the matrix.
- Communicate on a plan tuned to each quadrant.
Influence = informal authority — the power to facilitate or impede an objective; the ability to persuade or coerce others toward a course of action. Importance = formal authority — the priority given to satisfying that stakeholder's needs; their power to drive, change, or cancel the work.
Stakeholder Management Matrix (2×2)
Y = Influence (informal authority), X = Importance (formal authority):
| Low Importance | High Importance | |
|---|---|---|
| High Influence | Keep Satisfied | Manage Closely |
| Low Influence | Monitor | Keep Informed |
Communication plan — When / How
- When? How often · what stages · what depth.
- How? What format · what channel.
- Common errors to avoid: surprising stakeholders with bad news (ignore/delay/surprise); relying solely on email/electronic comms; delivering disparate status to different stakeholders.
Metric categories (pick what's meaningful per stakeholder)
- Value — LTV; LTV:CAC.
- Quality — defects; % test coverage; fix-to-feature ratio; return rate.
- Progress — lead & cycle time; velocity/burndown; % dependencies.
- Satisfaction — NPS; CSAT; renewal rate; time-to-value; customer effort (CES).
Interview the user (batch questions)
- Who are the stakeholders (people/groups) touched by this work?
- For each — how much influence (informal) and importance (formal) do they have?
- What outcome/metric does each one actually care about?
- What cadence and channel fits each (weekly meeting, email digest, dashboard)?
- What's the current status and any risks to surface?
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.
- 11d ago First seen · 99 lines · 107 tokens per session scan A 2345c73abe3d
pm-stakeholder-communication is a skill published in the GitHub repository julianoczkowski/product-manager (32 stars, last pushed 1mo ago), licensed MIT. It adds 107 tokens to every session and 1,198 once invoked, about $0.0005 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 skills, from other repositories
issues
Create GitHub issues from research findings as atomic deliverables. Orchestrates the issue-architect agent using the full swarm pattern (TeamCreate → TaskCreate → Agent(teamname) → SendMessage → TeamDelete). Use this skill when the user invokes /sigint:issues.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…