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 britt/agent-skills --skill stakeholder-updatesgit clone --depth 1 https://github.com/britt/agent-skillsWrote 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/britt/agent-skills/stakeholder-updates)<a href="https://agentmods.dev/skills/britt/agent-skills/stakeholder-updates"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/stakeholder-updates.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.00049 | $0.01263 |
| Opus 5 | $0.00024 | $0.00632 |
| Sonnet 5 | $0.00010 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
stakeholder-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 8d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Updates Skill
This skill helps craft effective communications for stakeholders at various levels.
When to Use
Activate this skill when:
- Writing status updates or progress reports
- Communicating delays or blockers
- Sharing launch announcements
- Requesting decisions or resources
- Reporting on milestones or outcomes
Do NOT use this skill for technical documentation or commit messages — it is for audience-facing status communication.
Core Principles
Know Your Audience
Executives (C-level):
- Lead with business impact
- Be concise (3-5 sentences)
- Include metrics and outcomes
- Avoid technical jargon
- Focus on "what" and "why", not "how"
Management (Directors, VPs):
- Balance detail with brevity
- Include both progress and blockers
- Provide context for decisions
- Mention resource needs
- Highlight risks and mitigation
Peers (Other PMs, Team Leads):
- Can be more detailed
- Include tactical information
- Share lessons learned
- Discuss trade-offs and alternatives
- Be transparent about challenges
Team Members:
- Provide full context
- Explain "why" behind decisions
- Share timelines and expectations
- Acknowledge contributions
- Be specific about next steps
Update Structure
Status Update Template
Subject/Title: [Concise summary of current state]
TL;DR: (1-2 sentences) Current status in plain language with key takeaway
Progress This Week:
- Completed: [specific accomplishments]
- In Progress: [active work with % complete]
- Planned Next: [upcoming priorities]
Metrics/Impact:
- [Quantifiable results or leading indicators]
Blockers/Risks:
- [Issue]: Impact and proposed resolution
Decisions Needed:
- [Decision]: Context, options, recommendation, deadline
Next Milestones:
- [Date]: [Milestone and success criteria]
Example: Team Update (Project Delay)
Subject: Q2 Mobile Release - Timeline Update
Context: We've hit an integration blocker with the third-party payment SDK that requires vendor support.
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.
- 8d ago First seen · 166 lines · 49 tokens per session scan A c2ba18d21df2
stakeholder-updates is a skill published in the GitHub repository britt/agent-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 1,263 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
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.