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 GiangGiangTran/ba-skills --skill stakeholder-managementgit clone --depth 1 https://github.com/GiangGiangTran/ba-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/gianggiangtran/ba-skills/stakeholder-management)<a href="https://agentmods.dev/skills/gianggiangtran/ba-skills/stakeholder-management"><img src="https://agentmods.dev/badge/skills/gianggiangtran/ba-skills/stakeholder-management/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/gianggiangtran/ba-skills/stakeholder-management"><img src="https://agentmods.dev/badge/skills/gianggiangtran/ba-skills/stakeholder-management.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.00043 | $0.02018 |
| Opus 5 | $0.00022 | $0.01009 |
| Sonnet 5 | $0.00009 | $0.00404 |
| Haiku 4.5 | $0.00004 | $0.00202 |
Grade A, and why
stakeholder-management 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.
How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Management for BA
Navigate complexity of multiple interests, personalities, and agendas.
What is Stakeholder Management?
Definition: Systematic process of identifying people with interest/influence in project, understanding their needs, managing expectations, and building coalitions for success.
Why it matters:
- Surprised stakeholders derail projects (scope creep, budget, timeline)
- Conflicting stakeholders paralyze decisions (executive vs user vs technical)
- Early engagement prevents late changes (expensive rework)
- Coalition building ensures support through challenges
When to Use:
- ✅ Starting new initiative (identify who matters)
- ✅ Major changes (manage resistance and concerns)
- ✅ Conflicting interests (negotiate competing needs)
- ✅ Before decision points (build consensus)
- ✅ Throughout project (keep stakeholders aligned)
Core Stakeholder Management Concepts
1. Power/Interest Matrix
Categorize stakeholders to determine engagement strategy.
HIGH INTEREST
|
MANAGE | MANAGE CLOSELY
SATISFACTI. | (Monthly updates,
| Include in decisions)
────────────────┼────────────────
|
MONITOR | KEEP SATISFIED
| (Quarterly updates,
| Consider preferences)
────────────────┼────────────────
LOW INTEREST
(Power →)
Placement:
- Manage Closely (High Power, High Interest): Sponsor, PM, Key user - involve in decisions
- Keep Satisfied (High Power, Low Interest): Finance, Legal - provide updates, prevent objections
- Manage Satisfaction (Low Power, High Interest): Team, Daily users - keep informed
- Monitor (Low Power, Low Interest): Peripheral users - minimal contact
2. Stakeholder Archetypes
Different types need different approaches:
| Archetype | Motivates | Concerns | Approach |
|---|---|---|---|
| Sponsor/Executive | ROI, timeline, budget | Risk, cost overruns | Data-driven, executive summary, business case |
| End User | Ease of use, solves problems | Change, learning curve | Demos, training, involvement in design |
| Technical Lead | Feasibility, architecture, quality | Technical debt, scalability | Technical discussion, trade-off explanations |
| Resistor | Status quo, job security | Risk to them personally | Listen, acknowledge concerns, show benefits to them |
| Champion | Success, solving real problems | Lack of support, visibility | Empower them, make them visible |
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.
- 11d ago First seen · 294 lines · 43 tokens per session scan A 32c1525710ea
stakeholder-management is a skill published in the GitHub repository GiangGiangTran/ba-skills (6 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 2,018 once invoked, about $0.0002 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.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.