multi-stakeholder-comm

multi-stakeholder-comm is a skill for Claude Code from Ludovic33Fr/product-ai-toolbox. It costs 50 tokens per session (1,733 once invoked), scanned A, original, MIT.

A French-language communication workflow that adapts one important cross-team message for different stakeholders, meaning people with different roles or concerns.

In plain words
What is it for?
Use it to create a separate one-page version of a roadmap change, major launch, structural decision, or alert for each stakeholder.
Why use it?
A single generic message may not address what technical, financial, commercial, or people-focused readers need to know.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pm-augmente plugin — 12 skills, 6 agents shipped together

Good fit Use it to create a separate one-page version of a roadmap change, major launch, structural decision, or alert for each stakeholder.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ludovic33fr/product-ai-toolbox/multi-stakeholder-comm
Install

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.

Any agent
npx skills add Ludovic33Fr/product-ai-toolbox --skill multi-stakeholder-comm
Clone the repo
git clone --depth 1 https://github.com/Ludovic33Fr/product-ai-toolbox

Made for: Claude Code.

Or install pm-augmente, the plugin that ships this one along with the rest of its 12 skills, 6 agents.

Wrote 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.

agentmods badge for multi-stakeholder-comm

README.md
[![agentmods](https://agentmods.dev/badge/skills/ludovic33fr/product-ai-toolbox/multi-stakeholder-comm/github.svg)](https://agentmods.dev/skills/ludovic33fr/product-ai-toolbox/multi-stakeholder-comm)
Your own site
<a href="https://agentmods.dev/skills/ludovic33fr/product-ai-toolbox/multi-stakeholder-comm"><img src="https://agentmods.dev/badge/skills/ludovic33fr/product-ai-toolbox/multi-stakeholder-comm/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.

agentmods 80×15 button for multi-stakeholder-comm

Your own site · 80×15
<a href="https://agentmods.dev/skills/ludovic33fr/product-ai-toolbox/multi-stakeholder-comm"><img src="https://agentmods.dev/badge/skills/ludovic33fr/product-ai-toolbox/multi-stakeholder-comm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,733 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01733
Opus 5 $0.00025 $0.00866
Sonnet 5 $0.00010 $0.00347
Haiku 4.5 $0.00005 $0.00173

Measured 11d ago against content hash 1b5700ac7cf8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

multi-stakeholder-comm 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.

skills/multi-stakeholder-comm/SKILL.md · 173 lines

How it starts

The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.

multi-stakeholder-comm

Fiche éditoriale

Objectif. Décliner un même sujet en versions calibrées par stakeholder.

Entrées. Contenu de fond, matrice stakeholders.

Sorties. Un encart d'une page par stakeholder, dans son format préféré.

Cadence d'usage. Avant chaque communication transverse importante.

Mode opératoire

Quand m'invoquer

L'utilisateur a un sujet à communiquer transversalement (changement de roadmap, lancement majeur, décision structurante, alerte) et veut éviter le mail unique générique. Il me fournit le contenu de fond et sa matrice stakeholders (nom, rôle, angle de préoccupation, format préféré).

Procédure

  1. Comprendre le contenu de fond : reformuler en mes mots les 3-5 points-clés. Si la reformulation ne tient pas, demander des précisions.
  2. Lire la matrice stakeholders : pour chaque destinataire, identifier rôle, angle (financier, technique, commercial, RH, etc.) et format préféré (mail synthétique, slide, dashboard, slack).
  3. Pour chaque stakeholder, générer un encart en respectant trois règles :
    • Une page maximum (densité adaptée au format).
    • L'angle de préoccupation est traité en premier.
    • Le format respecte la préférence (slide → bullets et titre fort ; mail → paragraphes courts ; slack → ton informel + emojis sobres).
  4. Cohérence factuelle : tous les encarts disent la même chose sur les faits. Ce qui varie, c'est l'ordre, l'angle, le niveau de détail technique, et la formulation.
  5. Indicateur de divergence : signaler si un même fait risquerait d'être interprété différemment selon le format choisi (ex : "M&A en discussion" peut sonner alarmant pour le CFO et opportuniste pour le CMO).
  6. Produire la sortie au format ci-dessous.

Format de sortie

# Communication transverse — {sujet}

## Points-clés (factuels, identiques pour tous)

1. ...
2. ...
3. ...

## Indicateurs de divergence à surveiller

- {fait susceptible d'être lu différemment} — vigilance pour {stakeholders A vs B}

---

## Encart pour {Stakeholder 1} — {rôle}, {angle de préoccupation}

*Format : {préférence}*

{Contenu calibré, ≤ 1 page.}

---

## Encart pour {Stakeholder 2} — {rôle}, {angle}

*Format : {préférence}*

{Contenu calibré.}

---

## Encart pour {Stakeholder 3} — ...
...

Read the full file on GitHub · 173 lines

Changes

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.

  1. 11d ago First seen · 173 lines · 50 tokens per session scan A 1b5700ac7cf8

Subscribe to this mod's changes

multi-stakeholder-comm is a skill published in the GitHub repository Ludovic33Fr/product-ai-toolbox (1 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 1,733 once invoked, about $0.0003 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.