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 rampstackco/claude-skills --skill stakeholder-communicationgit clone --depth 1 https://github.com/rampstackco/claude-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/skills/rampstackco/claude-skills/stakeholder-communication)<a href="https://agentmods.dev/skills/rampstackco/claude-skills/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/stakeholder-communication.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00103 | $0.02572 |
| Opus 5 | $0.00051 | $0.01286 |
| Sonnet 5 | $0.00021 | $0.00514 |
| Haiku 4.5 | $0.00010 | $0.00257 |
Grade A, and why
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- stakeholder-communication — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Communication
Get the right information to the right people at the right time, in a form they can act on. Stack-agnostic. Applies to any team operating with cross-functional stakeholders.
When to use
- Writing weekly or monthly status updates
- Preparing for an executive review or board update
- Sharing a technical decision with a non-technical audience
- Communicating a delay, miss, or quality problem
- Asking for help, resources, or decisions
- Managing up to a manager or sponsor
- Designing the communication cadence for a project
- Drafting an internal announcement
When NOT to use
- Customer-facing communication (use marketing/support skills)
- Public comms or press (different framework, different stakes)
- Incident communication during an active incident (use
incident-response) - Internal documentation that isn't time-sensitive (use
documentation-strategy) - Specific delivery formats (slide deck design, email tone) - this skill is about content and structure
Required inputs
- The audience (who specifically, what's their context, what do they care about)
- The purpose (inform, decide, escalate, ask, celebrate)
- The substance (what's actually happening)
- The medium (email, doc, meeting, slide, chat)
- Time constraints (when do they need this)
The framework: 5 questions
Before any stakeholder communication, answer:
Question 1: Who is the audience?
Specifically. "Leadership" is too vague. The CFO and the VP of Engineering have different concerns.
For each named audience:
- What do they care about? (revenue, risk, quality, velocity, costs, customers)
- What do they already know? (background you can skip)
- What's their level of detail tolerance? (executives want headlines; ICs want details)
- What action do you want from them? (acknowledgment, decision, help, no action)
Question 2: What's the headline?
If they read only one sentence, what should they take away?
The headline goes first. Always. The narrative supports it; the data confirms it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 361 lines · 103 tokens per session scan A a3686760ebe7
stakeholder-communication is a skill published in the GitHub repository rampstackco/claude-skills (826 stars, last pushed 10d ago), licensed MIT. It adds 103 tokens to every session and 2,572 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-09-03.
Other skills, from other repositories
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.
agent-teams
Team composition knowledge for Claude Code Agent Teams - when to suggest teams, optimal sizing, spawn prompt patterns.
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…