What is stakeholder-mapping?

A way to list people and roles affected by an engagement and assess their influence, interest, and attitude. An engagement is a project or relationship involving an organization and its stakeholders.

Use it when starting an engagement, identifying important contacts, finding likely supporters or blockers, and organizing stakeholders on an influence-and-interest grid.

It clarifies who can approve, fund, block, or be affected by the work. This helps determine who needs close attention, regular updates, or monitoring.

stakeholder-mapping — Skill for Claude Code and Codex by mizukaizen

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 mizukaizen/hive-doctrine-mcp --skill stakeholder-mapping

Clone the repo

git clone --depth 1 https://github.com/mizukaizen/hive-doctrine-mcp

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/stakeholder-mapping/github.svg)](https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/stakeholder-mapping)

Your own site

<a href="https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/stakeholder-mapping"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/stakeholder-mapping/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/stakeholder-mapping"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/stakeholder-mapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 496 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00496
Opus 5.5	$0.00000	$0.00198
Sonnet 5.5	$0.00000	$0.00099
Haiku 4.5	$0.00000	$0.00050

Measured 2mo ago against content hash 2c3c07add8df, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

stakeholder-mapping 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 2mo 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.

gated-products/honey/claude-packages/HD-4005-consultant/skills/stakeholder-mapping/SKILL.md · 61 lines

How it starts

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

Stakeholder Mapping Skill

Use when starting an engagement. Maps stakeholders by influence/interest, identifies champions and blockers.

When to Activate

User asks to "map stakeholders" or "identify stakeholders"
The /new-engagement command is invoked
User mentions needing to understand "who matters" or "who to talk to"

Process

Identify stakeholders. From available context (engagement brief, org charts, meeting notes), list every person or role that could affect or be affected by the engagement.
Classify each stakeholder. For each, assess:
- Influence (High/Low): Can they approve, block, fund, or redirect the engagement?
- Interest (High/Low): Do they care about the outcome? Will it affect their work?
- Disposition (Champion/Neutral/Blocker): Are they supportive, indifferent, or resistant?
Plot the grid.

                    HIGH INTEREST
                         |
    Keep Informed        |        Manage Closely
    (champions live      |        (decision makers,
     here often)         |         sponsors)
                         |
   LOW INFLUENCE --------+-------- HIGH INFLUENCE
                         |
    Monitor              |        Keep Satisfied
    (minimal effort)     |        (brief updates,
                         |         no surprises)
                         |
                    LOW INTEREST

Define engagement strategy. For each quadrant, specify:
- Communication frequency (weekly/fortnightly/monthly/as-needed)
- Communication format (meeting/email/report/dashboard)
- Key messages tailored to their concerns
- Risk if they are neglected
Identify dynamics.
- Who are the informal influencers (not in the org chart but respected)?
- Are there alliances or tensions between stakeholders?
- Who controls budget vs who controls access vs who controls narrative?

Output

A stakeholder map document saved to scope/stakeholder-map.md with:

Stakeholder list with classifications
2x2 grid placement
Engagement strategy per quadrant
Key risks and mitigation for blocker stakeholders

Read the full file on GitHub · 61 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.

2mo ago First seen · 61 lines · 0 tokens per session scan A 2c3c07add8df

Subscribe to this mod's changes

stakeholder-mapping is a skill published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 496 tokens. 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.

AI Safety Multi-Agent Planning Project management agent-marketplace ai-agents mcp mcp-server

stakeholder-mapping next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
stakeholder-mappingmizukaizen/hive-doctrine-mcp	Skill	0	4mo ago	MIT	A	0	Claude Code, Codex
jev-desktopopenwong2kim/wmux	Skill	448	yesterday	MIT	A	125	Claude Code, Codex
agent-desktop-ffiopenwong2kim/wmux	Skill	448	yesterday	MIT	A	122	Claude Code, Codex
agent-desktopopenwong2kim/wmux	Skill	448	yesterday	MIT	A	161	Claude Code, Codex
agent-desktop-macosopenwong2kim/wmux	Skill	448	yesterday	MIT	A	115	Claude Code, Codex
agent-desktop-windowsopenwong2kim/wmux	Skill	448	yesterday	MIT	A	119	Claude Code, Codex
coding-agents-farmgriddynamics/rosetta	Skill	373	yesterday	Apache-2.0	B	32	Claude Code