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 gleanwork/cursor-plugins --skill stakeholdersgit clone --depth 1 https://github.com/gleanwork/cursor-pluginsWrote 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/gleanwork/cursor-plugins/stakeholders)<a href="https://agentmods.dev/skills/gleanwork/cursor-plugins/stakeholders"><img src="https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/stakeholders/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/gleanwork/cursor-plugins/stakeholders"><img src="https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/stakeholders.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.00072 | $0.01264 |
| Opus 5.5 | $0.00029 | $0.00506 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to stakeholders — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 164 lines · 72 tokens per session scan A 40db23480b9d
stakeholders is a skill published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 17d ago), licensed MIT. It adds 72 tokens to every session and 1,264 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to stakeholders, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…