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 agentmods add skills/gleanwork/claude-plugins/stakeholdersnpx skills add gleanwork/claude-plugins --skill stakeholdersgit clone --depth 1 https://github.com/gleanwork/claude-pluginsWhat 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 | $0.00072 | $0.01264 |
| Opus 5 | $0.00036 | $0.00632 |
| Sonnet 5 | $0.00014 | $0.00253 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
stakeholders 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- stakeholders — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Discovery
You are helping someone identify the right people to involve in a change, decision, or project.
Determine the change, project, or decision from the user's request. If it is absent or unclear, ask the user to clarify — for example: what type of change (technical, process, or both), what is the scope (single team, cross-team, company-wide), and what systems or components will be affected.
Core Principles
- Quality over quantity: Don't list everyone tangentially related
- Distinguish roles: Approvers vs. consultants vs. FYI recipients
- Be skeptical: Just because someone's name appears doesn't make them a stakeholder
- Fewer is better: A focused list is more useful than a comprehensive one
Phase 1: Understand the Change
Goal: Clarify what's being changed and why
If the change is vague, ask the user to clarify:
- What type of change is this? (Technical change, process change, or both)
- What's the scope? (Single team, cross-team, company-wide)
- What systems or components will this affect?
Phase 2: Find Stakeholders
Goal: Identify technical owners, decision makers, and affected parties
-
Start with Glean chat for a synthesized stakeholder view:
chat "Who are the stakeholders for [change/system]? Include code owners, decision makers, and teams that depend on this." -
Gather specific details with direct searches:
code_search "[affected system] contributors" search "[affected system] RFC OR architecture doc" employee_search "[affected system] team lead OR manager" -
Search for downstream dependencies:
search "[affected system] integration OR dependency OR consumer"
Phase 3: Vet Each Stakeholder (CRITICAL)
Goal: Filter to people who genuinely need to be involved — BE SKEPTICAL
| Test | ✅ Include | ⚠️ Caution | ❌ Reject |
|---|---|---|---|
| Direct Impact | Owns affected code, manages affected team, depends on affected system | Works in same general area, different systems | Mentioned topic once |
| Authority | 🔴 Approver: Has explicit sign-off | 🟡 Consultant: Should be consulted | 🟢 FYI: Should know | Unclear role | No clear reason to involve them |
| Relevance | Currently owns area, actively maintains system | Recently changed roles — confirm still relevant | Former owner, historical involvement only |
| Evidence | Named in CODEOWNERS, documented owner, explicit dependency | Mentioned in related docs — verify | Just keyword matches |
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.
- 2d ago First seen · 164 lines · 72 tokens per session scan A 40db23480b9d
stakeholders is a skill published in the GitHub repository gleanwork/claude-plugins (25 stars, last pushed 12d ago), licensed MIT. It adds 72 tokens to every session and 1,264 once invoked, about $0.0004 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.