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 liqiongyu/lenny_skills_plus --skill stakeholder-alignmentgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/stakeholder-alignment)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/stakeholder-alignment"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/stakeholder-alignment/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/liqiongyu/lenny_skills_plus/stakeholder-alignment"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/stakeholder-alignment.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.00023 | $0.02105 |
| Opus 5 | $0.00012 | $0.01052 |
| Sonnet 5 | $0.00005 | $0.00421 |
| Haiku 4.5 | $0.00002 | $0.00211 |
Grade A, and why
stakeholder-alignment 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Alignment
Scope
Covers
- Getting to shared understanding on goal, decision, and success criteria
- Mapping stakeholders (deciders/influencers/blockers) and tailoring messaging to what they care about
- Turning “opinions” into decision principles + evaluation criteria
- Running a no-surprises pre-brief loop to surface objections early
- Facilitating an alignment/decision meeting and locking follow-through with clear comms
When to use
- “Help me get exec buy-in for this roadmap change.”
- “We keep leaving meetings ‘aligned’ and then un-aligning—fix the process.”
- “Map stakeholders and create a plan to align them on a proposal.”
- “I need cross-functional alignment (Eng/Design/Sales/Legal) before we commit.”
- “Draft an alignment pre-read + meeting plan + follow-up comms.”
When NOT to use
- You don’t yet have a clear problem to solve (use problem definition first).
- You mainly need a decision framework/roles for a complex choice (use
running-decision-processes; this skill assumes you can name the decision and stakeholders). - You only need a polished deck or talk track (use
giving-presentations; this skill focuses on alignment mechanics and artifacts, not slide design). - The work is ongoing cross-functional coordination, not a discrete alignment push (use
cross-functional-collaboration). - You need to influence or manage your relationship with your manager specifically (use
managing-up). - The request is interpersonal/HR/legal or requires specialist counsel.
Inputs
Minimum required
- Alignment goal: inform / align / decide (and by when)
- The proposal (or decision) in one sentence + why now
- Stakeholder list (or org context to infer it)
- Constraints/non-negotiables (timeline, budget, policy, compliance, customer commitments)
- Current state: what’s already been discussed, and where alignment breaks down
Missing-info strategy
- Ask 3–5 questions from references/INTAKE.md at a time.
- If key info is unavailable, proceed with explicit assumptions and label unknowns.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- eval/eval_config.json 1.8 KB
- eval/SHOWCASE.md 5.7 KB
- eval/with_skill.md 33 KB
- eval/without_skill.md 25 KB
- README.md 1.0 KB
- references/CHECKLISTS.md 2.1 KB
- references/EXAMPLES.md 1.9 KB
- references/INTAKE.md 2.2 KB
- references/RUBRIC.md 3.6 KB
- references/SOURCE_SUMMARY.md 1.6 KB
- references/TEMPLATES.md 3.2 KB
- references/WORKFLOW.md 3.5 KB
- skillpack.json 382 B
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 · 133 lines · 23 tokens per session scan A 4c113270e326
stakeholder-alignment is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 2,105 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
exec-weekly-agenda-generator
Synthesize the past week across meetings, chat, email, and calendar to generate a ranked list of 5-10 topics for the weekly leadership team meeting. Use when the user asks to prep for their leadership meeting, generate meeting topics, build the agenda, or says "prep me for Monday.".
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.