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 killvxk/pm-skills-zh --skill stakeholder-mapgit clone --depth 1 https://github.com/killvxk/pm-skills-zhWrote 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/killvxk/pm-skills-zh/stakeholder-map)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/stakeholder-map"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/stakeholder-map/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/killvxk/pm-skills-zh/stakeholder-map"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/stakeholder-map.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.00057 | $0.00657 |
| Opus 5 | $0.00028 | $0.00329 |
| Sonnet 5 | $0.00011 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
stakeholder-map 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 9d 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.
What it actually says
干系人地图与沟通计划
在权力×利益方格上映射干系人，并为每个群体制定定制化沟通计划。
Context（背景）
你正在帮助为 $ARGUMENTS 构建干系人地图。
如果用户提供了文件（组织架构图、项目简报、团队名单），请先阅读。如果他们描述了产品或计划，用该背景信息推断可能的干系人。
Instructions（操作指南）
-
识别干系人：列出所有相关的个人和群体——高管、工程负责人、设计师、市场、销售、支持、法务、财务、外部合作伙伴和终端用户。
-
按两个维度对每位干系人进行分类：
- 权力（高/低）：影响决策、资源或成果的能力
- 关注度（高/低）：项目对其直接影响程度，或其参与积极性
-
将干系人放入权力×利益方格：
高关注度 低关注度 高权力 重点管理 — 定期一对一，参与决策，提前征询意见 保持满意 — 定期更新，仅上报关键问题 低权力 及时告知 — 定期状态更新，邀请参加演示，收集反馈 持续监控 — 轻量级更新，按需响应 -
针对每个象限，推荐：
- 沟通频率（每天、每周、每两周、每月）
- 沟通形式（一对一、邮件、Slack、会议、看板）
- 核心信息和表达框架
- 忽视此干系人的潜在风险
-
创建沟通计划表格：
干系人 角色 权力 关注度 策略 频率 渠道 核心信息 -
标注潜在冲突：识别利益存在竞争关系的干系人，并建议对齐策略。
逐步思考。将干系人地图保存为 Markdown 文档。
Further Reading（延伸阅读）
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.
- 9d ago First seen · 52 lines · 57 tokens per session scan A b9949b91f65a
stakeholder-map is a skill published in the GitHub repository killvxk/pm-skills-zh (156 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 657 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.