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 uthumany/uthy-legacy-os --skill stakeholder-communicationgit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/stakeholder-communication)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/stakeholder-communication/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/uthumany/uthy-legacy-os/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/stakeholder-communication.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.00030 | $0.00906 |
| Opus 5 | $0.00015 | $0.00453 |
| Sonnet 5 | $0.00006 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
stakeholder-communication 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 11d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Communication
Overview
Great product work + poor communication = perceived failure. This skill helps you communicate with stakeholders — executives, cross-functional teams, and customers — in ways that build trust, manage expectations, and keep everyone aligned.
When to Use
- Providing regular status updates on an initiative
- Communicating a delay, blocker, or risk
- Presenting results to leadership
- Onboarding a new stakeholder to your project
- Don't use for: day-to-day team standups (different audience, different format), marketing communications
Instructions
1. Know Your Audience
| Stakeholder | What They Care About | Format |
|---|---|---|
| Executives | Impact, risks, decisions needed | 2-3 sentence summary + RAG status |
| Cross-functional teams | Dependencies, timelines, action items | Bullet list with owners |
| Customers | What's changing, when, why | Release notes, blog posts |
| Your team | Progress, blockers, decisions | Standup, Slack update |
2. Use the RAG Status Framework
- 🟢 Green: On track. No blockers. Expected to ship on time.
- 🟡 Yellow: At risk. Blocker identified, plan to resolve exists, timeline may slip.
- 🔴 Red: Off track. Needs escalation. Timeline WILL slip without intervention.
3. Write the Status Update
Executive summary (3 sentences max):
- What happened since last update
- Current status (RAG + why)
- What you need from them
Details (if needed):
- Progress against goals (metrics if available)
- Key decisions made
- Risks and mitigations
- Upcoming milestones
4. Communicate Bad News
When things go wrong:
- Be early — Bad news doesn't get better with age
- State the problem clearly — What happened, what's the impact
- Bring a plan — What we're doing about it, what we need
- Timeline — When will we know more / when will it be fixed
- Own it — Blame doesn't help. Solutions do.
Template for bad news:
"We're going to miss the [date] launch for [feature]. Here's why: [reason]. Impact: [cost/scope]. Our plan: [mitigation]. We need from you: [decision/help]. Revised ETA: [new date]."
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.
- 11d ago First seen · 95 lines · 30 tokens per session scan A 7e07e057453d
stakeholder-communication is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 906 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…