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 shennawardana23/skillme --skill stakeholder-communication-and-status-updatesgit clone --depth 1 https://github.com/shennawardana23/skillmeWrote 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/shennawardana23/skillme/stakeholder-communication-and-status-updates)<a href="https://agentmods.dev/skills/shennawardana23/skillme/stakeholder-communication-and-status-updates"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/stakeholder-communication-and-status-updates/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/shennawardana23/skillme/stakeholder-communication-and-status-updates"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/stakeholder-communication-and-status-updates.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.00108 | $0.02222 |
| Opus 5 | $0.00054 | $0.01111 |
| Sonnet 5 | $0.00022 | $0.00444 |
| Haiku 4.5 | $0.00011 | $0.00222 |
Grade A, and why
stakeholder-communication-and-status-updates 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Communication and Status Updates
Write status updates and strategy memos as connected prose, not bullet fragments. Full sentences force you to state the causal or logical relationship between two facts; a bullet point lets you juxtapose them and imply a connection without ever having to defend it.
Why narrative beats bullets
A bullet list is a set of claims with no stated relationship between them. Two adjacent bullets —
- Signups grew 12% this month
- We shipped the new onboarding flow
— invite the reader to assume the second caused the first. Maybe it did. Maybe signups grew because of a marketing campaign and the onboarding flow actually hurt conversion. The bullet format never forces the writer to make the claim explicit, so it never gets checked. A sentence forces the choice:
"Signups grew 12% this month, driven primarily by the referral campaign; the new onboarding flow shipped mid-month and it's too early to isolate its effect on conversion."
That sentence is falsifiable — a reader can push back on "driven primarily by." The bullet pair was not falsifiable; it just sat there implying causation. This is the core mechanism, not a stylistic preference: writing prose exposes gaps in reasoning that the author would otherwise never notice, because a bullet never demands the connective tissue that a sentence grammatically requires.
The same mechanism catches fuzzy thinking at the whole-document level. Writing "we should prioritize X" as a sentence with a "because" clause forces you to actually have a reason. A slide titled "Prioritization" with X, Y, Z as sub-bullets underneath implies X, Y, Z were compared and X won — without ever showing the comparison.
Structure of a status/strategy narrative
Use this order for anything longer than a quick weekly note (a strategy memo, a quarterly review, a project deep-dive):
- Context — what this document is about and why the reader is reading it now. One paragraph. Assume the reader has forgotten details from last time; don't assume they remember your last update.
- What happened — the events and decisions since the last update, told as a sequence, not a status board. Include what you decided NOT to do and why, if it's relevant — omitted alternatives are exactly the kind of thing a bullet list quietly drops.
- Data — the numbers that support or complicate the "what happened" narrative, with enough surrounding sentence to say what the number means and whether it's good, bad, or ambiguous. A number without an interpretation is not information; state whether it's above, below, or in line with expectation.
- What's next — concrete next steps, owners, and rough timing, written as commitments, not aspirations ("we will" not "we hope to").
- Risks — see below. This section exists even when there's nothing alarming to report; "no material risks this period" is itself a claim worth stating explicitly rather than omitting.
What ships with it
1 file 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 · 181 lines · 108 tokens per session scan A 369b8e21892c
stakeholder-communication-and-status-updates is a skill published in the GitHub repository shennawardana23/skillme (2 stars, last pushed 15d ago), licensed Apache-2.0. It adds 108 tokens to every session and 2,222 once invoked, about $0.0005 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
autonomous-workflow
The phase-based machinery (0–7) behind the aw dispatcher — task intake through tested PR delivery in an isolated Git worktree, with optional companion skills for planning, quality gates, TDD, UX, code quality, docs, and CI verification. Companions skip silently if not installed. NOT the entry point and not…
batch-linear-tickets
Batch-analyze and resolve multiple Linear tickets — bug fixes and feature work. For each ticket: classifies as bug or feature (auto from Linear labels, or via the --type flag), dispatches the appropriate per-ticket analysis (linear-ticket-investigator + rca-investigator for bugs, just linear-ticket-investigator for…
aw
Ships autonomous, end-to-end coding work — implement a feature or fix, all the way to a tested draft PR — from a single opt-in entry point. Detects the task tier (Micro / Lite / Full) and routes: Micro/Lite run single-pass in this context; Full hands off to the aw-planner → aw-executor agents. Use when the user asks…
openspec-implementation
A workflow for implementing an approved technical specification one task at a time. It reads the proposal, makes the changes, runs tests, and validates the result.
codely-plan-create-github
Create a plan for the specified task and store it as GitHub issues in the repository of the current working directory. Given the URL of a GitHub issue, it turns that issue into the parent "plan" issue (Goal, Context and a checklist of phases) and creates one child issue per phase, linking every phase as a native…
codely-plan_phase-implement-github
Implement one phase of a plan stored as GitHub issues in the repository of the current working directory. Given the URL of a phase (child) issue it implements that phase; given the parent plan issue it finds and implements the current phase. Only implements a single phase per invocation, then stops for user review. It…