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 viktorbezdek/skillstack --skill stakeholder-alignmentgit clone --depth 1 https://github.com/viktorbezdek/skillstackWrote 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/viktorbezdek/skillstack/stakeholder-alignment)<a href="https://agentmods.dev/skills/viktorbezdek/skillstack/stakeholder-alignment"><img src="https://agentmods.dev/badge/skills/viktorbezdek/skillstack/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/viktorbezdek/skillstack/stakeholder-alignment"><img src="https://agentmods.dev/badge/skills/viktorbezdek/skillstack/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.00134 | $0.01963 |
| Opus 5.5 | $0.00054 | $0.00785 |
| Sonnet 5.5 | $0.00027 | $0.00393 |
| Haiku 4.5 | $0.00013 | $0.00196 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Alignment
Decisions fail more often in the alignment than in the logic. A good RFC or decision doc does two things: makes the best argument for the chosen path, and makes the roles of everyone affected explicit so no one is surprised.
Pick the right artifact
| Artifact | When to use | Length |
|---|---|---|
| RFC / design doc | Technical decision affecting multiple teams; invites comment | 3-10 pages |
| Proposal | Bet on a direction that requires budget/headcount/scope | 1-3 pages |
| Pre-read | Input for a scheduled decision meeting | 1-2 pages |
| Decision doc | Record a decision that has been made (or is being made now) | 1 page |
| One-pager | Early alignment on an idea before full RFC | 1 page |
Use the smallest artifact that produces alignment. A 10-page RFC for a two-team change is over-investment; a Slack thread for a 10-team change is under-investment.
RFC / design doc structure
# [Title] — [state: Draft / Reviewing / Accepted / Rejected / Superseded]
## BLUF
[One-paragraph summary: the problem, the proposed direction, the ask.]
## Roles (DACI)
- **Driver:** [who writes + shepherds]
- **Approver:** [who makes the final call — name, not group]
- **Contributors:** [who provides input]
- **Informed:** [who needs to know]
## Context
[Shared understanding. What led here. Keep controversial claims for later sections.]
## Problem
[What we are trying to solve. Why now.]
## Options considered
- Option A: [name] — [one paragraph] — pros / cons / rough cost
- Option B: [name] — [same]
- Option C: do nothing — [same]
## Recommendation
[Chosen option + why, in one paragraph.]
## Trade-offs
[What we are giving up. What we are not solving. Second-order effects.]
## Open questions
- [ ] [Question needing input] — @person
- [ ] [Assumption needing validation] — @person
## Plan
[Milestones with dates. Dependencies on other teams.]
## Appendix
[Supporting material, benchmarks, prior discussions.]
Variations: for short changes, collapse Options / Recommendation into one section. For contentious changes, expand Trade-offs with a pre-mortem.
What ships with it
5 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.
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 · 196 lines · 134 tokens per session scan A 6ddc4cdf39ad
stakeholder-alignment is a skill published in the GitHub repository viktorbezdek/skillstack (14 stars, last pushed 4mo ago), licensed MIT. It adds 134 tokens to every session and 1,963 once invoked, about $0.0005 per session on Opus 5.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
agents-v2-py
Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.
analytics-product
Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.
api-security-best-practices
Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities.
analytics-tracking
Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.
antigravity-workflows
Use when asked to ship a SaaS MVP, audit application security, build an AI agent, run browser QA, or design a domain model with multiple skills and verified checkpoints.
agent-tool-builder
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.