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 yezannnnn/agentGroup --skill stakeholder-updategit clone --depth 1 https://github.com/yezannnnn/agentGroupWrote 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/yezannnnn/agentgroup/stakeholder-update)<a href="https://agentmods.dev/skills/yezannnnn/agentgroup/stakeholder-update"><img src="https://agentmods.dev/badge/skills/yezannnnn/agentgroup/stakeholder-update/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/yezannnnn/agentgroup/stakeholder-update"><img src="https://agentmods.dev/badge/skills/yezannnnn/agentgroup/stakeholder-update.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.00040 | $0.01618 |
| Opus 5 | $0.00020 | $0.00809 |
| Sonnet 5 | $0.00008 | $0.00324 |
| Haiku 4.5 | $0.00004 | $0.00162 |
Grade A, and why
stakeholder-update 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 5d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Update Skill
This skill creates effective status updates for executives and stakeholders following the BLUF (Bottom Line Up Front) principle.
Update Structure
1. BLUF (Bottom Line Up Front)
Start with the most important information:
- Status: 🟢 On track / 🟡 At risk / 🔴 Blocked / ✅ Complete
- Key Takeaway: One sentence summary of current state
- Action Needed: What you need from stakeholders (if anything)
2. Progress Summary
Brief overview of accomplishments:
- What shipped this period
- Milestones achieved
- Key metrics movement
Keep to 3-5 bullet points maximum.
3. Metrics Dashboard
Key Metrics
| Metric | Current | Target | Trend | Status |
|---|---|---|---|---|
| [Metric name] | [Value] | [Target] | ↑/→/↓ | 🟢/🟡/🔴 |
Include 3-5 most important metrics only.
4. Risks & Blockers
High Priority Issues:
- Issue: Brief description
- Impact: What's at stake
- Mitigation: What you're doing about it
- Help Needed: What stakeholders can do (if applicable)
Only include issues that matter at executive level.
5. Upcoming Milestones
Next 30 Days:
- Milestone (expected date)
- Milestone (expected date)
Next 90 Days:
- Major milestone (month)
- Major milestone (month)
6. Decisions Needed (if applicable)
- Decision: Clear description
- Options: 2-3 options with pros/cons
- Recommendation: What you recommend and why
- Timeline: When decision is needed
Writing Guidelines
Tone: Professional, concise, action-oriented Length: Keep under 1 page (or 2 minutes reading time) Frequency: Weekly for active projects, bi-weekly for maintenance
Executive Communication Principles:
-
Lead with conclusions, not process
- ❌ "We ran 5 experiments this week and analyzed the data..."
- ✅ "Conversion rate increased 15% from optimization work"
-
Focus on impact, not activities
- ❌ "Held 12 customer interviews"
- ✅ "Identified #1 barrier to adoption (complexity of setup)"
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.
- 5d ago First seen · 220 lines · 40 tokens per session scan A 323dffad57fd
stakeholder-update is a skill published in the GitHub repository yezannnnn/agentGroup (149 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 1,618 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.