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 saski/arnesto --skill stakeholder-update-generatorgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/stakeholder-update-generator)<a href="https://agentmods.dev/skills/saski/arnesto/stakeholder-update-generator"><img src="https://agentmods.dev/badge/skills/saski/arnesto/stakeholder-update-generator.svg" alt="Measured on agentmods" 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.00027 | $0.00479 |
| Opus 5 | $0.00014 | $0.00239 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
stakeholder-update-generator 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 4d 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.
This is a copy
100% identical to stakeholder-update-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Stakeholder Update Generator
When to Use
- Shipping a new feature or product update
- Need to communicate progress to stakeholders
- Writing release notes for users
- Preparing status updates for leadership
- Documenting what changed in a sprint or milestone
What This Skill Does
Creates engaging, well-structured updates that communicate what shipped, why it matters, and what comes next.
Instructions
Help me write an engaging update for [product/feature/sprint] that is both informative and compelling. Include:
- High-level summary (2-3 sentences)
- Key accomplishments or new features
- Feature/item name
- Brief description
- User benefit and impact
- Improvements and fixes
- Metrics or results (if available)
- What's next
Style preference: [Professional/Casual/Technical] Audience: [Users/Leadership/Engineering/Investors]
Changes to document: [List what shipped, improvements made, or progress achieved]
Best Practices
- Lead with the most impactful changes
- Focus on user benefits, not technical details (unless technical audience)
- Use concrete metrics when possible ("50% faster" not "performance improvements")
- Keep the tone consistent with your brand
- Include visuals or screenshots if possible (note them in the text)
- Add a call-to-action if relevant
Example
Input: Shipped notification center, improved search performance, fixed 15 bugs Output: Structured update highlighting "Never miss an important update" (notification center benefits), "Find anything in seconds" (search improvements), professional tone, metrics included (3x faster search), next steps mentioned
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.
- 4d ago First seen · 64 lines · 27 tokens per session scan A 77fecb2f1cc7
stakeholder-update-generator is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed yesterday), licensed Unlicense. It adds 27 tokens to every session and 479 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to stakeholder-update-generator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
flowai-live-dashboard-template
Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity sparklines, and a top-contributors panel, all in a single self-contained HTML file with light/dark theming, hoverable…
code-import
Read an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.
team-okrs
OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar. Use when the brief mentions "OKRs", "key results", "objectives", or "目标".
huashu-keynote-black
OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.