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 mizukaizen/hive-doctrine-mcp --skill stakeholder-mappinggit clone --depth 1 https://github.com/mizukaizen/hive-doctrine-mcpWrote 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/mizukaizen/hive-doctrine-mcp/stakeholder-mapping)<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.
<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>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 | $0.00000 | $0.00248 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
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 10d 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 — 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-engagementcommand 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
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.
- 10d ago First seen · 61 lines · 0 tokens per session scan A 2c3c07add8df
stakeholder-mapping is a skill published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 2mo 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.
Other skills, from other repositories
writbase-recipes
WritBase API recipes reference (internal).
extract-tasks
Review conversation and extract untracked work items as WritBase tasks (writbase:info, writbase:addtask). Use at end of session to capture untracked work.
loop
Poll WritBase for top tasks and work through them autonomously. Use when you want to process the task queue, auto-work, or run the work loop.
writbase-router
Route task, writbase, agent, permission, provenance, webhook, and delegation requests to WritBase MCP tools. Triggers on keywords like task, writbase, work, assign, delegate, permission, audit, webhook, subscribe, provenance, agent key.
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…