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 KirKruglov/claude-skills-kit --skill stakeholder-adaptergit clone --depth 1 https://github.com/KirKruglov/claude-skills-kitWrote 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/kirkruglov/claude-skills-kit/stakeholder-adapter)<a href="https://agentmods.dev/skills/kirkruglov/claude-skills-kit/stakeholder-adapter"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-skills-kit/stakeholder-adapter/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/kirkruglov/claude-skills-kit/stakeholder-adapter"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-skills-kit/stakeholder-adapter.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.00135 | $0.01774 |
| Opus 5 | $0.00068 | $0.00887 |
| Sonnet 5 | $0.00027 | $0.00355 |
| Haiku 4.5 | $0.00014 | $0.00177 |
Grade A, and why
stakeholder-adapter 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: stakeholder-adapter
Adapts any working document into audience-specific versions for Leadership, Engineering/Team, and Client — applying the right framing, length, and vocabulary for each reader without rewriting from scratch.
Target audience: product managers, team leads, project managers, business analysts.
Triggers
English: "adapt document", "stakeholder adapter", "create executive version", "make a client version", "rewrite for audience", "tailor this for", "I need different versions of this document", "adapt for leadership", "create team version", "prepare versions for different audiences"
Russian: «адаптируй документ», «перепиши для аудитории», «сделай версию для руководства», «сделай версию для команды», «сделай версию для клиента», «адаптируй для стейкхолдеров», «разные версии документа», «подготовь версии для разных аудиторий»
Language Detection
Detect the language of the source document — produce adapted versions in that language. If the user explicitly requests a different language, use it. If the source document language is unclear, use the language of the user's request.
Input
Required: source document — pasted as text in the conversation, or provided as a local file path (.md or .txt).
Optional:
- Target audience selection (if not provided, ask via AskUserQuestion)
- Document type (status update, PRD, proposal, meeting notes, other)
- Key message that must appear in every adapted version
Output
One clearly labeled section per selected audience, presented in chat.
Optionally, files saved to the working directory on user request:
stakeholder-adapter-[audience]-YYYY-MM-DD.md
Instructions
Step 0 — Extract context from the trigger
Before asking questions, check what the user already provided in their message:
- Document text included → extract it
- Target audiences mentioned (e.g., "for leadership and the client") → extract them
- Document type mentioned → extract it
What ships with it
4 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.
- 9d ago First seen · 180 lines · 135 tokens per session scan A 92cc16dbae52
stakeholder-adapter is a skill published in the GitHub repository KirKruglov/claude-skills-kit (18 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 1,774 once invoked, about $0.0007 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
github-issue-creator
Turn error logs, screenshots, voice notes, and rough bug reports into crisp, developer-ready GitHub issues with repro steps, impact, and evidence.
onboarding-planner
TRIGGER THIS when preparing for new hires, planning first-day/week/month activities, creating onboarding schedules, building 30-60-90 day plans, designing welcome programs, organizing training schedules, or setting up buddy/mentorship programs. Designs comprehensive, engaging onboarding experiences that accelerate…
performance-review-assistant
TRIGGER THIS when conducting performance reviews, writing manager feedback, creating self-assessments, building peer feedback, developing PIPs, creating development plans, or handling difficult performance conversations. Helps write constructive, specific, actionable feedback that develops performance and documents…
roadmap-builder
Build product roadmaps with quarterly planning, feature prioritization, dependency mapping, and stakeholder alignment. Create actionable roadmaps that communicate strategy and guide execution.
sprint-planning
Plan sprints with story point estimation, capacity planning, sprint goals, and retrospective frameworks. Organize teams for effective iteration with clear goals, realistic commitments, and continuous improvement.
onboarding-playbook
Design customer onboarding playbooks with milestone tracking, training plans, health checks, and success criteria.